From: Ted Ts'o <tytso@mit.edu>
To: john stultz <johnstul@us.ibm.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
ocfs2-devel@oss.oracle.com, Keith Maanthey <kmannth@us.ibm.com>,
Eric Whitney <eric.whitney@hp.com>
Subject: [Ocfs2-devel] [PATCH -v2 0/3] jbd2 scalability patches
Date: Thu, 5 Aug 2010 01:42:11 -0400 [thread overview]
Message-ID: <20100805054211.GF2901@thunk.org> (raw)
In-Reply-To: <1280973537.2678.37.camel@localhost.localdomain>
Thanks, John, for doing these numbers!!!
> vfs + j_state lock + jdb2 scalability queue
> Throughput 1214.21 MB/sec 8 procs
> Throughput 1175.49 MB/sec 4 procs
> Throughput 716.294 MB/sec 2 procs
> Throughput 402.988 MB/sec 1 procs
2.6.35-rc6-vfs + atomic
Throughput 2648.42 MB/sec 8 procs
Throughput 1586.68 MB/sec 4 procs
Throughput 851.545 MB/sec 2 procs
Throughput 453.106 MB/sec 1 procs
Your earlier numbers were quite a bit higher than this latest set. I
assume that's due to hardware differences?
- Ted
next prev parent reply other threads:[~2010-08-05 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 16:39 [Ocfs2-devel] [PATCH -v2 0/3] jbd2 scalability patches Theodore Ts'o
2010-08-04 16:39 ` [Ocfs2-devel] [PATCH -v2 1/3] jbd2: Use atomic variables to avoid taking t_handle_lock in jbd2_journal_stop Theodore Ts'o
2010-08-09 17:02 ` Jan Kara
2010-08-09 19:05 ` Ted Ts'o
2010-08-09 19:45 ` Jan Kara
2010-08-10 16:30 ` Ted Ts'o
2010-08-11 22:16 ` Jan Kara
2010-08-04 16:39 ` [Ocfs2-devel] [PATCH -v2 2/3] jbd2: Change j_state_lock to be a rwlock_t Theodore Ts'o
2010-08-04 16:39 ` [Ocfs2-devel] [PATCH -v2 3/3] jbd2: Remove t_handle_lock from start_this_handle() Theodore Ts'o
2010-08-05 1:58 ` [Ocfs2-devel] [PATCH -v2 0/3] jbd2 scalability patches john stultz
2010-08-05 5:42 ` Ted Ts'o [this message]
2010-08-05 17:42 ` john stultz
2010-08-09 16:06 ` Joel Becker
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=20100805054211.GF2901@thunk.org \
--to=tytso@mit.edu \
--cc=eric.whitney@hp.com \
--cc=johnstul@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
/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).