CEPH filesystem development
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Patrick McGarry <patrick@inktank.com>,
	Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Re: Bobtail vs Argonaut Performance Preview
Date: Sat, 22 Dec 2012 13:44:15 -0600	[thread overview]
Message-ID: <50D60D8F.6020708@inktank.com> (raw)
In-Reply-To: <20121222184508.GA32567@infradead.org>

On 12/22/2012 12:45 PM, Christoph Hellwig wrote:
> On Sat, Dec 22, 2012 at 07:36:41AM -0600, Mark Nelson wrote:
>> Btw Christoph, thank you for taking the time to read my article.  If
>> I've done anything dumb or suboptimal regarding xfs, please do let
>> me know.  Soon I will be doing parametric sweeps over ceph parameter
>> spaces to see how performance varies on different hardware
>> configurations.  I want to make sure the tests are setup as
>> optimally as possible.
>
> You're defintively missing the "inode64" mount option, which we've
> always recommended, and which finally made it to be the default in
> Linux 3.7.
>

Is inode64 typically faster than inode32?  I thought I remembered 
dchinner saying that the situation wasn't always particularly clear and 
it depended on the workload.  Having said that, I can't really see it 
not being a good thing for Ceph to spread metadata out over all of the 
AGs, especially in the multi-disk raid config.  I'll use it for the next 
set of tests.

> Some other things worth playing with, but which aren't guaranteed to
> be a win are:
>
>   - use a larger than default log size (e.g. mkfs.xfs -l size=2g)
>   - use large directory blocks, similar to what you already do for btrfs
>     (mkfs.xfs -n size=16k or 64k)

I'll definitely give them a try at some point.  Thanks for the tips 
Christoph!

>
> Also at least for the benchmarks doing concurrent I/O (or any real life
> setup) you're probably much better off with a concatenation than a RAID 0
> for the multiple disk setup.
>



  reply	other threads:[~2012-12-22 19:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 16:08 Bobtail vs Argonaut Performance Preview Patrick McGarry
2012-12-22  8:32 ` Christoph Hellwig
2012-12-22 13:36   ` Mark Nelson
2012-12-22 16:28     ` Patrick McGarry
2012-12-22 18:45     ` Christoph Hellwig
2012-12-22 19:44       ` Mark Nelson [this message]
2012-12-22 19:46         ` Christoph Hellwig
2012-12-27 22:17       ` Stefan Priebe

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=50D60D8F.6020708@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=patrick@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox