All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Eric Whitney's ext4 scaling data
Date: Tue, 26 Mar 2013 00:00:48 -0400	[thread overview]
Message-ID: <nsxhajyzu6n.fsf@closure.thunk.org> (raw)


Eric Whitney has very thoughtfully provided an updated set of ext4
scalability data (with comparisons against ext3, xfs, and btrfs)
comparing performance between 3.1 and 3.2, and comparing performance
between 3.2 and 3.6-rc3.

I've made his compressed tar file available at:

https://www.kernel.org/pub/linux/kernel/people/tytso/ext4_scaling_data.tar.xz
https://www.kernel.org/pub/linux/kernel/people/tytso/ext4_scaling_data.tar.gz

His comments on this data are:

   It contains two sets of data - one comparing 3.2 and 3.1 (this was
   the last data set I posted publicly) and another comparing 3.6-rc3
   and 3.2.  3.6-rc3 was the last data set I collected, and until now, I
   hadn't prepared graphs for it.  The graphical results are consistent
   with what I'd reported verbally over the first 2/3 of last year - not
   much change between 3.2 and 3.6-rc3.  The last large change I could
   see occurred in 3.2, as mentioned in the notes.

   The tarball unpacks into a directory named ext4_scaling_data and
   contains a few subdirectories.  The directories named 3.2 and 3.6-rc3
   map to the data sets described above.  Each contains a file named
   index.html which you can open with a web browser to see the graphs,
   browse the raw data, ffsb profiles and lockstats, etc.

   Hopefully you'll find the lockstats and other information useful,
   even though stale (3.6-rc3 became available the last week in August
   2012).

Thanks, Eric for making this data available!

                                                - Ted

P.S.  The btrfs numbers were shockingly bad, even for the random write
workload, which was unexpected for me.  I wonder if checksumming was
enabled by default, or some such, and this was hampering their
performance...

             reply	other threads:[~2013-03-26  4:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  4:00 Theodore Ts'o [this message]
     [not found] ` <alpine.LFD.2.00.1303261555140.2455@(none)>
2013-03-27  3:29   ` Eric Whitney's ext4 scaling data Theodore Ts'o
2013-03-27  3:33 ` Zheng Liu
2013-03-27  3:35   ` Theodore Ts'o
2013-03-27  7:21     ` Zheng Liu
2013-03-27 15:10       ` Theodore Ts'o
2013-03-28  4:49         ` Zheng Liu
2013-03-28  5:14         ` Dave Chinner
2013-04-01  3:43           ` Eric Whitney
2013-03-28  5:07     ` 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=nsxhajyzu6n.fsf@closure.thunk.org \
    --to=tytso@mit.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.