From: Eric Whitney <eric.whitney@hp.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: 3.1-rc2 and 3.0 filesystem scalability measurements
Date: Fri, 09 Sep 2011 19:35:58 -0400 [thread overview]
Message-ID: <4E6AA2DE.2060903@hp.com> (raw)
(Several filesystem developers have asked that I post this on the
fsdevel as well the ext4 mailing lists.)
I've posted the results of some 3.1-rc2 / 3.0 ext4 scalability
measurements and comparisons on a 48 core x86_64 server at:
http://free.linux.hp.com/~enw/ext4/3.1-rc2
This includes throughput and CPU efficiency graphs for five simple
workloads, the raw data for same, and lockstats as well. The data have
been useful in improving ext4 scalability in the past.
The data cover ext4 filesystems with and without journals. For
reference, ext3, xfs, and btrfs are included as well.
The most notable improvement in this data is a significant scalability
gain for xfs when running the large_file_creates workload (the lockstats
suggest a behavioral change). This was first visible in 3.1-rc1. ext4
remains relatively unchanged.
Dave Chinner has asked that I make some changes to the way I collect xfs
data, and I'll try to address those before I post again.
Thanks,
Eric
reply other threads:[~2011-09-09 23:36 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=4E6AA2DE.2060903@hp.com \
--to=eric.whitney@hp.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).