From: Eric Whitney <eric.whitney@hp.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: 3.2 and 3.1 filesystem scalability measurements
Date: Sun, 29 Jan 2012 23:09:43 -0500 [thread overview]
Message-ID: <4F261807.2060108@hp.com> (raw)
I've posted the results of some 3.2 and 3.1 ext4 scalability
measurements and comparisons on a 48 core x86-64 server at:
http://free.linux.hp.com/~enw/ext4/3.2
This includes throughput and CPU efficiency graphs for five simple
workloads, the raw data for same, plus lockstats on ext4 filesystems
with and without journals. The data have been useful in improving ext4
scalability as a function of core and thread count in the past.
For reference, ext3, xfs, and btrfs data are also included.
The most notable improvement in 3.2 is a big scalability gain for
journaled ext4 when running the large_file_creates workload. This
bisects cleanly to Wu Fengguang's IO-less balance_dirty_pages() patch
which was included in the 3.2 merge window.
(Please note that the test system's hardware and firmware configuration
has changed since my last posting, so this data set cannot be directly
compared with my older sets.)
Thanks,
Eric
next reply other threads:[~2012-01-30 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 4:09 Eric Whitney [this message]
2012-01-30 15:13 ` 3.2 and 3.1 filesystem scalability measurements aziro.linux.adm
2012-01-30 20:30 ` Andreas Dilger
2012-01-31 0:14 ` Dave Chinner
2012-01-31 10:53 ` Jan Kara
2012-01-31 12:55 ` Wu Fengguang
2012-01-31 20:27 ` Dave Chinner
[not found] ` <20120131112726.GC3867@localhost>
2012-01-31 20:40 ` Dave Chinner
2012-01-30 15:36 ` Cédric Villemain
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=4F261807.2060108@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).