From: Hans Reiser <reiser@namesys.com>
To: "David C. Hansen" <haveblue@us.ibm.com>
Cc: David Lang <david.lang@digitalinsight.com>,
"Robert L. Harris" <Robert.L.Harris@rdlg.net>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Oleg Drokin <green@namesys.com>
Subject: Re: Reiser vs EXT3
Date: Fri, 01 Nov 2002 01:14:16 +0300 [thread overview]
Message-ID: <3DC1AB38.1040107@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210311248030.25405-100000@dlang.diginsite.com>
David C. Hansen wrote:
>On Thu, 2002-10-31 at 13:51, Hans Reiser wrote:
>
>
>>If you want to talk about 2.6 then you should talk about reiser4 not
>>reiserfs v3, and reiser4 is 7.6 times the write performance of ext3 for
>>30 copies of the linux kernel source code using modern IDE drives and
>>modern processors on a dual-CPU box, so I don't think any amount of
>>improved scalability will make ext3 competitive with reiser4 for
>>performance usages.
>>
>>We haven't had anyone test performance using RAID yet for reiser4, that
>>could be fun.
>>
>>
>
>I have a 14-drive hardware RAID array on an 8-proc box. Is that the
>kind of thing you want testing on? If you want to send me some testing
>scripts, I'll run them.
>
>
>
Yes, that would be cool.
Green, please respond to this email with details for him.
--
Hans
next prev parent reply other threads:[~2002-10-31 22:11 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
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 [this message]
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=3DC1AB38.1040107@namesys.com \
--to=reiser@namesys.com \
--cc=Robert.L.Harris@rdlg.net \
--cc=david.lang@digitalinsight.com \
--cc=green@namesys.com \
--cc=haveblue@us.ibm.com \
--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