From: Stefan Priebe <s.priebe@profihost.ag>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mark Nelson <mark.nelson@inktank.com>,
Patrick McGarry <patrick@inktank.com>,
Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Re: Bobtail vs Argonaut Performance Preview
Date: Thu, 27 Dec 2012 23:17:41 +0100 [thread overview]
Message-ID: <50DCC905.7000106@profihost.ag> (raw)
In-Reply-To: <20121222184508.GA32567@infradead.org>
Hi Christoph,
Am 22.12.2012 19:45, schrieb Christoph Hellwig:
> 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)
Thanks for recommendations.
Right now i'm using this in my ceph setup with 240GB SSDs for each OSD.
May i ask you to comment them? Do they make sense in your eyes?
# i have 12 cores per machine
mkfs.xfs -f -d agcount=12 /dev/sdX2
Mount options: noatime,nodiratime,nobarrier,logbsize=256k,logbufs=8,inode64
Greets,
Stefan
prev parent reply other threads:[~2012-12-27 22:17 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
2012-12-22 19:46 ` Christoph Hellwig
2012-12-27 22:17 ` Stefan Priebe [this message]
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=50DCC905.7000106@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox