From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Hans Reiser <reiser@namesys.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Reiserfs-List@namesys.com
Subject: Re: Reiser vs EXT3
Date: Thu, 31 Oct 2002 23:52:07 +0100 [thread overview]
Message-ID: <200210312352.07122.Dieter.Nuetzel@hamburg.de> (raw)
Am Donnerstag, 31. Oktober 2002 22:05 schrieb Jeff Garzik:
> 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.
>
> What is the read performance like?
>From his mentioned paper http://www.namesys.com/v4/fast_reiser4.html, it is
more then doubled compared to ext3 and ReiserFS v3.
To be fair he should explain if it was compared to the latest ext3 (htree)
stuff or not, yet.
It looks truly impressive.
Regards,
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel at hamburg.de (replace at with @)
next reply other threads:[~2002-10-31 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 22:52 Dieter Nützel [this message]
2002-11-01 1:16 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2002-11-01 0:51 Kevin Brosius
2002-10-31 14:19 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:14 ` Hans Reiser
2002-10-31 22:13 ` David C. Hansen
2002-10-31 20:23 ` Samuel Flory
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=200210312352.07122.Dieter.Nuetzel@hamburg.de \
--to=dieter.nuetzel@hamburg.de \
--cc=Reiserfs-List@namesys.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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
all inboxes | Powered by JetHome®