From: Phillip Susi <psusi@ubuntu.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Mitch Harder <mitch.harder@sabayonlinux.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Varying Leafsize and Nodesize in Btrfs
Date: Thu, 11 Oct 2012 13:58:50 -0400 [thread overview]
Message-ID: <507708DA.3040804@ubuntu.com> (raw)
In-Reply-To: <20120830162512.GA2879@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8/30/2012 12:25 PM, Josef Bacik wrote:
> Once you cross some hardware dependant threshold (usually past 32k)
> you start incurring high memmove() overhead in most workloads.
> Like all benchmarking its good to test your workload and see what
> works best, but 16k should generally be the best option. Thanks,
>
> Josef
Why are memmove()s neccesary, can they be avoided, and why do they
incur more overhead with 32k+ sizes?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQdwjZAAoJEJrBOlT6nu75rkYH/RYXBbAJfIG2KmmmFA8kSIiL
EEvdA9KRnVH08h2lnB26xNdCPbf59M7GrH2hZK48gM9x4OQPzKXf8eCTYTy4mFKy
mqTPFsgcPveTFtgoRXkuhZvUXMpFV4M8I7MLZRCcxk5KWTwA/slcunQxG7BMz/V4
tBxE8ya2Hxej2VJe4AbLR6PJbvCGsFXNlxBpUy9Qh7q0TmDeGzsoaZ1We1itNjQZ
wWjTerka2qe9dyP8EOUp/uZqGUQXu1TUKbTLygsfMb11/vGMkoUkZtTa0f9lQosw
10UlA8TyqAkLX3gpQzsJVCwiRuNWQBbQqvdYq3dCQOgzBbvOdvD6TtmeS1saO4o=
=qV0c
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-11 17:58 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
2012-10-11 17:58 ` Phillip Susi [this message]
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=507708DA.3040804@ubuntu.com \
--to=psusi@ubuntu.com \
--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).