From: Steven Pratt <slpratt@austin.ibm.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: New perf results
Date: Mon, 16 Nov 2009 16:26:28 -0600 [thread overview]
Message-ID: <4B01D194.9040605@austin.ibm.com> (raw)
New performance results have been uploaded for recent runs, including
the nodatasum option and a refresh of other file systems on current kernel.
http://btrfs.boxacle.net/repository/raid/history/History.html
No big surprises here, with the possible exception of the impact of
csums. For example 128 thread sequential read increased from about
380MB/sec to 630MB/sec by skipping checksums. This happened even though
we were only using about 40% cpu in the normal case. So, even though we
are not CPU bound, the overhead of checksums introduces some major
performance penalties.
Chris, are most of your runs on Nehelam based systems? I know we had
some different results on some tests and wonder if this is one of the
causes. Not sure when/if I can move up to a newer system.
Also some updates to the single disk system as well, although I am
lagging getting all the runs in on that box.
http://btrfs.boxacle.net/repository/single-disk/History/History.html
Steve
reply other threads:[~2009-11-16 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B01D194.9040605@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=linux-btrfs@vger.kernel.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