From: Vladimir Bashkirtsev <vladimir@bashkirtsev.com>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Calvin Morrow <calvin.morrow@gmail.com>,
Tommi Virtanen <tv@inktank.com>,
Josh Durgin <josh.durgin@inktank.com>,
ceph-devel@vger.kernel.org
Subject: Re: Poor read performance in KVM
Date: Fri, 20 Jul 2012 14:54:30 +0930 [thread overview]
Message-ID: <5008EB8E.30708@bashkirtsev.com> (raw)
In-Reply-To: <50084EC3.60003@inktank.com>
>
> 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. :)
>
Just confirming that one of our clients has run fair amount (on
gigabytes scale) of mysql updates in preceding few days. So it appears
all performance degradation stems from random writes. Perhaps I will
rebuild each osd to check if it would help to recover.
next prev parent reply other threads:[~2012-07-20 5:24 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
2012-07-20 5:24 ` Vladimir Bashkirtsev [this message]
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=5008EB8E.30708@bashkirtsev.com \
--to=vladimir@bashkirtsev.com \
--cc=calvin.morrow@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=mark.nelson@inktank.com \
--cc=tv@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.