From: "David C. Hansen" <haveblue@us.ibm.com>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Reiser vs EXT3
Date: 31 Oct 2002 11:02:49 -0800 [thread overview]
Message-ID: <1036090969.4272.59.camel@nighthawk> (raw)
In-Reply-To: <20021031141950.GM3420@rdlg.net>
On Thu, 2002-10-31 at 06:19, Robert L. Harris wrote:
>
> Still working on that replacement mail server and a new rumor has hit
> the mix. It follows that reiserfs is much faster than ext3 (made ext3,
> not converted from ext2 if it matters) and this is causing some
> problems. On a 200Gig filesystem is this truely an issue?
ext3 has some SMP scalability problems. The BKL is used to protect many
journal operations, and we see huge amounts of CPU spent spinning on it
on 4/8/16 proc machines. So much CPU, that it masks anything else we're
doing on the system. But, on a single-proc or just a 2-way, you
probably won't see much of this to be significant.
We haven't tested reiser extensively here, but from what I've seen it
scales much, much better than ext3 (as does jfs and probably xfs too).
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-10-31 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 14:19 Reiser vs EXT3 Robert L. Harris
2002-10-31 19:02 ` David C. Hansen [this message]
2002-10-31 20:49 ` David Lang
2002-10-31 21:51 ` Hans Reiser
2002-10-31 22:05 ` Jeff Garzik
2002-10-31 23:03 ` Matthew Kirkwood
2002-10-31 22:10 ` David C. Hansen
2002-10-31 22:13 ` David C. Hansen
2002-10-31 22:14 ` Hans Reiser
2002-10-31 20:23 ` Samuel Flory
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 22:52 Dieter Nützel
2002-11-01 1:16 ` David Lang
2002-11-01 0:51 Kevin Brosius
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=1036090969.4272.59.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=Robert.L.Harris@rdlg.net \
--cc=linux-kernel@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