From: Eric Whitney <eric.whitney@hp.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: 2.6.39 and 3.0 scalability measurement results
Date: Sun, 31 Jul 2011 22:57:52 -0400 [thread overview]
Message-ID: <4E361630.9060907@hp.com> (raw)
I've posted the results of my 2.6.38/2.6.39 and 2.6.39/3.0 ext4
scalability measurements and comparisons on a 48 core x86_64 server at:
http://free.linux.hp.com/~enw/ext4/2.6.39
http://free.linux.hp.com/~enw/ext4/3.0
The results include throughput and CPU efficiency graphs for five simple
workloads, the raw data for same, and lockstats as well.
The data cover ext4 filesystems with and without journals. For
reference, ext3, xfs, and btrfs are included as well.
The 2.6.38/2.6.39 results mainly show the clear scalability benefit of
making the mblk_io_submit mount option default behavior for ext4
filesystems with journals - see the large_file_creates throughput plot.
In the way of more recent news, the 2.6.39/3.0 results indicate little
change for ext4 either with or without journals.
Thanks,
Eric
next reply other threads:[~2011-08-01 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 2:57 Eric Whitney [this message]
2011-08-02 0:50 ` 2.6.39 and 3.0 scalability measurement results Dave Chinner
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=4E361630.9060907@hp.com \
--to=eric.whitney@hp.com \
--cc=linux-ext4@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).