All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	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:45:08 -0500	[thread overview]
Message-ID: <20121222184508.GA32567@infradead.org> (raw)
In-Reply-To: <50D5B769.4090104@inktank.com>

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.

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)

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.


  parent reply	other threads:[~2012-12-22 18:45 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 [this message]
2012-12-22 19:44       ` Mark Nelson
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=20121222184508.GA32567@infradead.org \
    --to=hch@infradead.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.com \
    --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 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.