All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: reiserfs-list@namesys.com, rufus@hackish.org
Subject: Re: Again, some bad Reiser4 (ReiserFS) 'reviews'
Date: Thu, 15 Jul 2004 10:56:24 -0700	[thread overview]
Message-ID: <40F6C548.7030805@namesys.com> (raw)
In-Reply-To: <200407150025.30908.Dieter.Nuetzel@hamburg.de>

Dieter Nützel wrote:

>http://rufus.hackish.org/wiki/2.6FileSystemBenchmarks
>
>Greetings,
>	Dieter
>
>
>  
>
I think he has an fsync intensive workload, which reiser4 is not good at 
because we haven't bothered with it yet, and we care more about maturing 
the atomic functionality.  I have no idea what ccache does with the fs.  
Does it use fsync?

How he got tar to be slow is hard to understand, I don't remember seeing 
a slow tar using reiser4, does anyone else?  I am guessing he created 
the tarball using ext2, and didn't know that readdir order matters and 
affects the tarball, and that he should create it on the filesystem 
being benchmarked.  Maybe the tarball ordering also affects subsequent 
compiles, I don't know.

zam, would you confirm that the fibration plugin is our current default 
plugin?

Hans

  parent reply	other threads:[~2004-07-15 17:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 22:25 Again, some bad Reiser4 (ReiserFS) 'reviews' Dieter Nützel
2004-07-15  2:34 ` Reiser4 InterMezzo reimplementation? David Masover
2004-07-15 17:56 ` Hans Reiser [this message]
2004-07-15 18:22   ` Again, some bad Reiser4 (ReiserFS) 'reviews' Alex Zarochentsev
2004-07-16  9:29     ` mjt
2004-07-16 19:52       ` David Masover
2004-07-17  4:32         ` Hans Reiser
2004-07-17  4:43       ` Hans Reiser
2004-07-17 16:07         ` Nikita Danilov
2004-07-18  6:44           ` Hans Reiser
2004-07-19  9:42             ` Francesco Biscani
2004-07-19 11:52   ` Redeeman
2004-07-19 17:49     ` Hans Reiser
2004-08-02 17:09   ` Peter Nelson

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=40F6C548.7030805@namesys.com \
    --to=reiser@namesys.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=reiserfs-list@namesys.com \
    --cc=rufus@hackish.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.