From: Roman Mamedov <rm@romanrm.ru>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org, Josef Bacik <jbacik@fusionio.com>,
Mitch Harder <mitch.harder@sabayonlinux.org>
Subject: Re: Varying Leafsize and Nodesize in Btrfs
Date: Fri, 31 Aug 2012 11:02:34 +0600 [thread overview]
Message-ID: <20120831110234.031e23ee@natsu> (raw)
In-Reply-To: <201208302334.49399.Martin@lichtvoll.de>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Thu, 30 Aug 2012 23:34:49 +0200
Martin Steigerwald <Martin@lichtvoll.de> wrote:
> I wanted to ask about 32k either.
>
> I used 32k on one 2,5 inch external esata disk. But I never measured
> anything so far.
>
> I wonder what a good value for SSD might be. I tend to not use anymore
> than 16k, but thats just some gut feeling right now. Nothing based on a
> well-founded explaination.
If you look closely at https://oss.oracle.com/~mason/blocksizes/ , you will
notice that 16K delivers almost all of the 32K's performance gains in "Read",
while not suffering from slowdowns that 32K shows in "Create" and "Delete".
I have chosen 16K for my new /home partition (on an SSD+HDD mdadm RAID1).
But what disappointed me at the time, is that one can't seem to have a "mixed"
allocation FS with non-default leaf/node sizes.
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-08-31 5:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 15:18 Varying Leafsize and Nodesize in Btrfs Mitch Harder
2012-08-30 16:25 ` Josef Bacik
2012-08-30 21:34 ` Martin Steigerwald
2012-08-30 21:50 ` Josef Bacik
2012-08-31 0:01 ` Chris Mason
2012-08-31 5:02 ` Roman Mamedov [this message]
2012-10-11 17:58 ` Phillip Susi
2012-10-12 10:32 ` Martin Steigerwald
2012-10-12 12:52 ` Martin Steigerwald
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=20120831110234.031e23ee@natsu \
--to=rm@romanrm.ru \
--cc=Martin@lichtvoll.de \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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).