linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: Mike Fedyk <mfedyk@mikefedyk.com>
Cc: Josef Bacik <josef@redhat.com>, Chris Samuel <chris@csamuel.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: Btrfs-progs: Update man page for mixed data+metadata option.
Date: Fri, 12 Nov 2010 09:59:32 -0600	[thread overview]
Message-ID: <AANLkTikt6F8jNKqGbG9AOfgX1bRgxRdUpq2DfeUjudBR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikvR_1Jpz6unuuGDWSB0eUoNMFMeL-zUQyw1FOz@mail.gmail.com>

On Fri, Nov 12, 2010 at 4:44 AM, Mike Fedyk <mfedyk@mikefedyk.com> wrot=
e:
> On Thu, Nov 11, 2010 at 11:41 PM, Josef Bacik <josef@redhat.com> wrot=
e:
>> On Fri, Nov 12, 2010 at 05:47:14PM +1100, Chris Samuel wrote:
>>> On 11/11/10 23:52, Josef Bacik wrote:
>>>
>>> > This feature incurs a performance penalty in larger filesystems, =
it is
>>> > recommended for use with filesystems of 1 GiB or smaller.
>>>
>>> Maybe slightly stronger, for example:
>>>
>>> This feature incurs a performance penalty for larger filesystems an=
d it
>>> is ONLY recommended for use with filesystems of 1 GiB or smaller.
>>>
>>> Is it worth having a check and a warning printed if a user does
>>> try and make a filesystem larger than 1GiB with this option ?
>>>
>>> Just in case they don't RTFM...
>>>
>>
>> No because depending on your usage it's actually kind of usefull for=
 anything
>> less than 5 GiB, and you're only looking at about a 5-10% perf degre=
dation when
>> using it on larger filesystems. =A0Thanks,
>>
>
> Then a warning of 10% slowdown if > 10GB would be good. =A0It's
> surprising how many will just read some forum post and not concern
> themselves with the docs at all.
>
> And making them type "yes" if > 100GB is probably a good idea too...
>

Just for clarification, you'll probably see a ~5-10% slowdown for any
size partition, not just "if > 10 GB"

But for smaller filesystems (~<5 GiB), you may want to accept the
performance penalty for more efficient disk space utilization.

=46or really small filesystems (~<1 GiB), using Btrfs defaults can
really start to impact on space utilization.  So the parent
data+metadata patch currently forces the data+metadata option on <1
GiB.

The Wiki is probably a better place for more extensive discussion of
the merits and trade-offs of this option.

The user still needs to actively "opt-in" to this option (unless their
partition is < GiB), and the man page will indicate a performance
penalty is incurred.

=46or something as important as changing your filesystem default
settings, it seems fair to expect the user has done their homework
when changing from the default setting.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-11-12 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 18:02 Btrfs-progs: Update man page for mixed data+metadata option Mitch Harder
2010-11-11  2:10 ` Josef Bacik
2010-11-11  3:53   ` Mitch Harder
2010-11-11  3:59     ` C Anthony Risinger
2010-11-11 12:52     ` Josef Bacik
2010-11-12  6:47       ` Chris Samuel
2010-11-12  7:41         ` Josef Bacik
2010-11-12 10:44           ` Mike Fedyk
2010-11-12 14:28             ` Marek Otahal
2010-11-12 16:56               ` Mike Fedyk
2010-11-15 16:28                 ` Mitch Harder
2010-11-12 15:59             ` Mitch Harder [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=AANLkTikt6F8jNKqGbG9AOfgX1bRgxRdUpq2DfeUjudBR@mail.gmail.com \
    --to=mitch.harder@sabayonlinux.org \
    --cc=chris@csamuel.org \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mfedyk@mikefedyk.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;
as well as URLs for NNTP newsgroup(s).