From: Stefan Priebe <s.priebe@profihost.ag>
To: Gregory Farnum <greg@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: btrfs big metadata
Date: Mon, 02 Jul 2012 19:40:09 +0200 [thread overview]
Message-ID: <4FF1DCF9.6050604@profihost.ag> (raw)
In-Reply-To: <CAPYLRzjDHf7m3BujRPw=BB_XHqrRqshgHjRetSqrb-EPF4GgXg@mail.gmail.com>
Am 02.07.2012 18:42, schrieb Gregory Farnum:
> On Sun, Jul 1, 2012 at 11:56 PM, Stefan Priebe - Profihost AG
> <s.priebe@profihost.ag> wrote:
>> Hello list,
>>
>> i found several people who use big metadata -n 64k -l 64k for ceph. But i
>> haven't found any ceph doc or info why to use this?
>>
>> What's the reason to use big metadata feature with ceph?
>
> One of the big problems users have had with Ceph-on-btrfs is that
> Ceph's usage patterns cause btrfs to dramatically fragment its
> metadata. Big metadata blocks reduce this fragmentation to a level
> where some users find it faster than xfs (which it previously wasn't).
Thanks!
Stefan
prev parent reply other threads:[~2012-07-02 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 6:56 btrfs big metadata Stefan Priebe - Profihost AG
2012-07-02 16:42 ` Gregory Farnum
2012-07-02 17:40 ` 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=4FF1DCF9.6050604@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@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.