From: Johannes Hirte <johannes.hirte@datenkhaos.de>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: "Swâmi Petaramesh" <swami@petaramesh.org>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS setup advice for laptop performance ?
Date: Mon, 7 Apr 2014 14:18:41 +0200 [thread overview]
Message-ID: <20140407141841.476f8aae@datenkhaos.de> (raw)
In-Reply-To: <533EA686.5030909@gmail.com>
On Fri, 04 Apr 2014 08:33:10 -0400
Austin S Hemmelgarn <ahferroin7@gmail.com> wrote:
> On 2014-04-04 04:02, Swâmi Petaramesh wrote:
> > - Is it still recommended to mkfs with a nodesize or leafsize
> > different (bigger) than the default ? I wouldn't like to lose too
> > much disk space anyway (1/2 nodesize per file on average ?), as it
> > will be limited...
> This depends on many things, the average size of the files on the disk
> is the biggest factor. In general you should get the best disk
> utilization by setting nodesize so that a majority of the files are
> less than the leafsize minus 256 bytes, and all but a few are smaller
> than two times the leafsize minus 256 bytes. However, if you want to
> really benefit from the data compression, you should just use the
> smallest leaf/nodesize for your system (which is what mkfs defaults
> to), as data that gets as BTRFS stores files whose size is at least
> (roughly) 256 bytes less than the leafsize inline with the metadata,
> and doesn't compress such files.
With commit c652e4efb8e2dd76ef1627d8cd649c6af5905902 the default
node-/leafsize has changed:
commit c652e4efb8e2dd76ef1627d8cd649c6af5905902
Author: Chris Mason <chris.mason@fusionio.com>
Date: Fri Nov 8 13:51:52 2013 -0500
mkfs: change default metadata blocksize to 16KB
next prev parent reply other threads:[~2014-04-07 12:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:02 BTRFS setup advice for laptop performance ? Swâmi Petaramesh
2014-04-04 12:33 ` Austin S Hemmelgarn
2014-04-04 12:48 ` Swâmi Petaramesh
2014-04-04 15:51 ` Austin S Hemmelgarn
2014-04-04 20:31 ` Duncan
2014-04-07 12:18 ` Johannes Hirte [this message]
2014-04-04 15:09 ` Hugo Mills
2014-04-04 22:35 ` Swâmi Petaramesh
2014-04-05 10:12 ` Duncan
2014-04-05 11:10 ` Swâmi Petaramesh
2014-04-05 12:16 ` Duncan
2014-04-05 14:13 ` Hugo Mills
2014-04-06 9:24 ` Swâmi Petaramesh
2014-04-07 15:11 ` Austin S Hemmelgarn
2014-04-08 11:56 ` Clemens Eisserer
2014-04-08 12:05 ` Austin S Hemmelgarn
2014-04-09 10:53 ` Chris Samuel
2014-04-12 13:17 ` Marc MERLIN
2014-04-12 17:12 ` Koen Kooi
2014-04-05 14:26 ` Garry T. Williams
2014-04-05 15:06 ` Duncan
2014-04-06 15:17 ` Martin Steigerwald
2014-04-09 11:08 ` Chris Samuel
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=20140407141841.476f8aae@datenkhaos.de \
--to=johannes.hirte@datenkhaos.de \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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 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.