From: Mark Nelson <mark.nelson@inktank.com>
To: Tommi Virtanen <tv@inktank.com>
Cc: Gregory Farnum <greg@inktank.com>,
bryan@virginia.edu, ceph-devel@vger.kernel.org
Subject: Re: Slow ceph fs performance
Date: Mon, 01 Oct 2012 12:03:59 -0500 [thread overview]
Message-ID: <5069CCFF.5040701@inktank.com> (raw)
In-Reply-To: <CADvuQRFS8VBt9aCtAMB_NADd0b3RGyuY5FMcyVRx5heksKQB_Q@mail.gmail.com>
On 10/01/2012 11:47 AM, Tommi Virtanen wrote:
> On Thu, Sep 27, 2012 at 11:04 AM, Gregory Farnum<greg@inktank.com> wrote:
>> However, my suspicion is that you're limited by metadata throughput
>> here. How large are your files? There might be some MDS or client
>> tunables we can adjust, but rsync's workload is a known weak spot for
>> CephFS.
>
> I feel like people are missing this part of Greg's message. Everyone
> is so busy benchmarking RADOS small I/O, but what if it's currently
> bottlenecked by all the file-level access operations that interact
> with the MDS? Rsync causes a ton of those.
>
> If you want to benchmark just the small IO, you can't compare rsync to rsync.
>
> If you want to benchmark just the metadata part, rsync with 0-size
> files might actually be an interesting workload.
I guess most of the small IO testing we've seen/done has been without
CephFS at all. It's entirely possible that the MDS is slowing things
down with an rsync workload like this on a fresh filesystem though.
Having said that, I don't like the way that our small IO performance
behaves (especially over time) when doing something like RADOS Bench.
It definitely seems like there is some pretty nasty underlying
filesystem metadata fragmentation or something going on after a while.
Mark
next prev parent reply other threads:[~2012-10-01 17:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 14:50 Slow ceph fs performance Bryan K. Wright
2012-09-26 15:26 ` Mark Nelson
2012-09-26 20:54 ` Bryan K. Wright
2012-09-27 15:16 ` Bryan K. Wright
2012-09-27 18:04 ` Gregory Farnum
2012-09-27 18:47 ` Bryan K. Wright
2012-09-27 19:47 ` Gregory Farnum
2012-10-01 16:47 ` Tommi Virtanen
2012-10-01 17:00 ` Gregory Farnum
2012-10-03 14:55 ` Bryan K. Wright
2012-10-03 18:35 ` Gregory Farnum
2012-10-04 13:14 ` Bryan K. Wright
2012-10-04 15:24 ` Sage Weil
2012-10-04 15:54 ` Bryan K. Wright
2012-10-26 20:48 ` Gregory Farnum
2012-10-29 15:08 ` Bryan K. Wright
2012-11-03 17:55 ` Gregory Farnum
2012-10-01 17:03 ` Mark Nelson [this message]
2012-09-27 23:40 ` Mark Kirkwood
2012-09-27 23:49 ` Mark Kirkwood
2012-09-28 12:22 ` mark seger
2012-10-01 15:41 ` Bryan K. Wright
2012-10-01 16:43 ` Mark Nelson
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=5069CCFF.5040701@inktank.com \
--to=mark.nelson@inktank.com \
--cc=bryan@virginia.edu \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@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.