linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: Holger Hoffstaette <holger.hoffstaette@googlemail.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: User feedback: raise the default leaf size to 16k
Date: Sun, 3 Mar 2013 11:36:20 -0500	[thread overview]
Message-ID: <20130303163620.GD18135@shiny.masoncoding.com> (raw)
In-Reply-To: <513326FA.3070607@swiftspirit.co.za>

On Sun, Mar 03, 2013 at 03:33:30AM -0700, Brendan Hide wrote:
> On 2013/02/13 12:33 PM, Holger Hoffstaette wrote:
> > - raise the leaf size to 16k
> > - use single metadata profile
> >
> > ...
> >
> > the difference in behaviour on a single disk is *very* noticeable.
> Did you try an isolated change of leaf size? I think the devs would be 
> willing to look into the default size if it makes a dramatic difference 
> on its own. Personally I think you are seeing an improvement more as a 
> result of the metadata profile rather than the leafsize.
> 
> I don't think changing the default profile for metadata will be easily 
> entertained as this is very important for protecting against corruption 
> due to bitrot.

The long term plan is to set the default size to 16K, since this does
cut down on metadata fragmentation.  But in some benchmarks, it adds lock
contention because we have fewer blocks to spread the locks over.

The 3.9 merge window has fixes for lock contention, so I need to
benchmark things again.

-chris

      reply	other threads:[~2013-03-03 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 10:33 User feedback: raise the default leaf size to 16k Holger Hoffstaette
2013-03-03 10:33 ` Brendan Hide
2013-03-03 16:36   ` Chris Mason [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=20130303163620.GD18135@shiny.masoncoding.com \
    --to=chris.mason@fusionio.com \
    --cc=brendan@swiftspirit.co.za \
    --cc=holger.hoffstaette@googlemail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).