From: Mark Nelson <mark.nelson@inktank.com>
To: Calvin Morrow <calvin.morrow@gmail.com>
Cc: Tommi Virtanen <tv@inktank.com>,
Vladimir Bashkirtsev <vladimir@bashkirtsev.com>,
Josh Durgin <josh.durgin@inktank.com>,
ceph-devel@vger.kernel.org
Subject: Re: Poor read performance in KVM
Date: Thu, 19 Jul 2012 13:15:31 -0500 [thread overview]
Message-ID: <50084EC3.60003@inktank.com> (raw)
In-Reply-To: <CADxhoDT8rimSwP+Y75tGVo3Nd5WYw8xHyDxBAMV8tb5no0OP4Q@mail.gmail.com>
On 07/19/2012 01:06 PM, Calvin Morrow wrote:
> On Thu, Jul 19, 2012 at 9:52 AM, Tommi Virtanen<tv@inktank.com> wrote:
>>
>> On Thu, Jul 19, 2012 at 5:19 AM, Vladimir Bashkirtsev
>> <vladimir@bashkirtsev.com> wrote:
>>> Look like that osd.0 performs with low latency but osd.1 latency is way
>>> too
>>> high and on average it appears as 200ms. osd is backed by btrfs over
>>> LVM2.
>>> May be issue lie in backing fs selection? All four osds running similar
>>
>> Our typical experience with btrfs right now seems to be that it works
>> fast when the filesystem is fresh, but as it ages, it starts to have
>> higher and higher delays on syncing writes. This does not seem to be
>> completely deterministic, that is, if you run many btrfs'es, the
>> symptoms start to appear at different times on different instances.
>
> Is Inktank seeing the slowdown on btrfs volumes with large metadata
> (32k / 64k) node/leaf sizes as well, or only on default (4k) sizes?
>
> Vladmir,
>
> What node/leaf size are you using on your btrfs volume?
Hi Vladmir,
We are seeing degradation at 64k node/leaf sizes as well. So far the
degradation is most obvious with small writes. it affects XFS as well,
though not as severely. We are vigorously looking into it. :)
Mark
>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Mark Nelson
Performance Engineer
Inktank
next prev parent reply other threads:[~2012-07-19 18:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 13:13 Poor read performance in KVM Vladimir Bashkirtsev
2012-07-16 6:16 ` Josh Durgin
2012-07-18 5:46 ` Vladimir Bashkirtsev
2012-07-18 15:27 ` Josh Durgin
2012-07-19 10:46 ` Vladimir Bashkirtsev
2012-07-19 12:19 ` Vladimir Bashkirtsev
2012-07-19 15:52 ` Tommi Virtanen
2012-07-19 18:06 ` Calvin Morrow
2012-07-19 18:15 ` Mark Nelson [this message]
2012-07-20 5:24 ` Vladimir Bashkirtsev
2012-07-20 5:24 ` Vladimir Bashkirtsev
2012-07-20 5:20 ` Vladimir Bashkirtsev
[not found] ` <50080D9D.8010306@bashkirtsev.com>
2012-07-19 18:42 ` Josh Durgin
2012-07-20 5:31 ` Vladimir Bashkirtsev
2012-07-20 16:17 ` Vladimir Bashkirtsev
2012-07-20 16:42 ` Tommi Virtanen
2012-07-20 16:53 ` Mark Nelson
2012-07-20 16:53 ` Vladimir Bashkirtsev
2012-07-29 15:31 ` Vladimir Bashkirtsev
2012-07-29 16:13 ` Mark Nelson
2012-07-18 15:34 ` Josh Durgin
2012-07-18 5:49 ` Vladimir Bashkirtsev
2012-07-18 5:51 ` Vladimir Bashkirtsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50084EC3.60003@inktank.com \
--to=mark.nelson@inktank.com \
--cc=calvin.morrow@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=tv@inktank.com \
--cc=vladimir@bashkirtsev.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox