All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: venom@sns.it
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	sglines@is-cs.com, linux-kernel@vger.kernel.org
Subject: Re: file system technical comparisons
Date: Tue, 06 Jan 2004 17:55:24 +0300	[thread overview]
Message-ID: <3FFACC5C.7050900@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0401061300550.13594-100000@cibs9.sns.it>

venom@sns.it wrote:

>What would be interesting is a new comparison between reiserFS reiser4 and
>latest XFS. To be onest I think ext3, with or withou HTree, obsolete, but it is
>abvious if you consider its origins, while I do not speack about JFS, since
>technically is interesting, but then the bench I did, more than an year ago,
>were not untisiasmant, and it was buggy when in a DIR there were too many
>"small" files.
>
>Luigi
>
>  
>
Actually I agree with you that JFS is architecturally much more 
interesting than ext3 (though Andrew Morton's readahead code for ext* is 
beautiful stuff).  I haven't really looked at why JFS is slow, though 
usually being slow at <100k sized files in a journaling filesystem is 
due to the journaling code.  The thing about performance is that the 
mistakes count for 4x what the things done right count for.  Chris Mason 
did a lot for V3's performance compared to the competition by writing 
nice journaling code for us.

htree has performance problems that are due to its architecture --- I 
think this is why they don't make it on by default --- it actually slows 
ext3 down substantially for average directory sizes.....  you can see 
that on our benchmarks page, or just by copying around some copies of 
the linux kernel yourself with it on and off.

-- 
Hans



  reply	other threads:[~2004-01-06 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 21:38 file system technical comparisons Steve Glines
2004-01-05  9:42 ` venom
2004-01-05 11:04   ` Hans Reiser
2004-01-05 17:08     ` venom
2004-01-05 17:18       ` Hans Reiser
2004-01-06 11:58         ` venom
2004-01-06 12:07           ` Hans Reiser
2004-01-06 23:48             ` venom
2004-01-07  9:13               ` Hans Reiser
2004-01-05 17:37   ` Randy.Dunlap
2004-01-06 12:04     ` venom
2004-01-06 14:55       ` Hans Reiser [this message]
2004-01-06 20:32         ` Theodore Ts'o
2004-01-09 19:32 ` Stewart Smith

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=3FFACC5C.7050900@namesys.com \
    --to=reiser@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=sglines@is-cs.com \
    --cc=venom@sns.it \
    /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.