public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul P Komkoff Jr <i@stingr.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: ext2-devel@lists.sourceforge.net
Subject: Re: [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1
Date: Wed, 2 Oct 2002 14:48:59 +0400	[thread overview]
Message-ID: <20021002104859.GD6318@stingr.net> (raw)
In-Reply-To: <20021001204330.GO3000@clusterfs.com>

Replying to Andreas Dilger:
> Why do you think data=writeback is better than data=journal?  If the
> files have no data then it should not make a difference.

It is better than default data=ordered I think :)

Thanks for detailed explanation - it saved much time for me and
accortind to yours directions I have recalculated my test. Now ext3 is
better :)

e3
create		2m49.545s	0m4.162s	2m20.766s
delete		2m8.155s	0m3.614s	1m34.945s

reiser
create		3m13.577s	0m4.338s	2m54.026s
delete		4m39.249s	0m3.968s 	4m16.297s

e3
create		2m50.766s	0m4.024s	2m21.197s
delete		2m8.755s	0m3.501s	1m35.737s

reiser
create		3m13.015s	0m4.432s	2m53.412s
delete		4m41.011s	0m3.893s	4m16.845s


this is two typical runs. Now I creating ext3 with
mke2fs -j -O dir_index -J size=192 -T news /dev/sda4

as you can see, this improves performance by 1/4

Unfortunately, there still one issue in ext3. It called "inode limit".
Initially I wanted to run this test on 1000000 files but ... I hit
inode limit and don't want to increase it artificially yet.

Reiserfs worked fine because it don't have such kind of limit ...

-- 
Paul P 'Stingray' Komkoff 'Greatest' Jr /// (icq)23200764 /// (http)stingr.net
  When you're invisible, the only one really watching you is you (my keychain)

  parent reply	other threads:[~2002-10-02 10:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 19:59 [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1 Paul P Komkoff Jr
2002-10-01 20:43 ` Hans Reiser
2002-10-01 20:49   ` Hans Reiser
2002-10-01 21:17     ` Rik van Riel
2002-10-01 21:31     ` Daniel Phillips
2002-10-01 20:43 ` Andreas Dilger
2002-10-01 21:19   ` Hans Reiser
2002-10-02 10:48   ` Paul P Komkoff Jr [this message]
2002-10-02 16:54     ` Andreas Dilger
2002-10-03  0:37       ` [Ext2-devel] " Theodore Ts'o
2002-10-03 12:04         ` Hans Reiser
2002-10-03 19:40           ` Theodore Ts'o
2002-10-03 19:44             ` Hans Reiser
2002-10-04 15:53   ` Oleg Drokin
2002-10-04 17:09     ` [Ext2-devel] " Andreas Dilger
2002-10-07  6:54       ` Oleg Drokin
2002-10-10  0:27       ` Daniel Phillips
2002-10-01 21:27 ` Daniel Phillips
2002-10-02 16:38   ` Paul P Komkoff Jr
2002-10-02  6:39 ` Nikita Danilov

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=20021002104859.GD6318@stingr.net \
    --to=i@stingr.net \
    --cc=ext2-devel@lists.sourceforge.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