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 <reiserfs-list@namesys.com>,
	Chris Mason <mason@suse.com>, Paul P Komkoff Jr <i@stingr.net>,
	Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Subject: Re: Re: [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1
Date: Sat, 05 Oct 2002 02:27:20 +0400	[thread overview]
Message-ID: <3D9E15C8.2060005@namesys.com> (raw)
In-Reply-To: 200210042254.23978.Dieter.Nuetzel@hamburg.de

Dieter Nützel wrote:

>Am Mittwoch, 2. Oktober 2002 10:48 schrieb Paul P Komkoff Jr:
>  
>
>>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 ...
>>    
>>
>
>Orange and apples, again?
>
>Try with latest ReiserFS data-logging and see what we get?
>Chris do you have something for 2.5.40+ ready?
>
>2.5.40 is GREAT!
>
>Regards,
>	Dieter
>  
>
So, I think that if you create enough files in your test to stress the 
IO subsystem, then it will be a much more interesting test. 
 Unfortunately, you may need to increase the inode allocation to test 
this for ext3.  Once you start to get above a million files, you may 
start to see reiser4 doing substantially better than ReiserFS because 
reiser4 has better layout and better hashes based on things we learned.

I would be curious to see your benchmark done for 3 million files.  I 
would be curious to see what happens if you umount in the middle of it. 
 I would not be surprised if interesting VFS/dcache performance issues 
arise as you increase the number of files.

Hans



      parent reply	other threads:[~2002-10-04 22:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 20:54 [STUPID TESTCASE] ext3 htree vs. reiserfs on 2.5.40-mm1 Dieter Nützel
2002-10-04 21:28 ` 2.5.40 (was " Valdis.Kletnieks
2002-10-04 21:54   ` Ed Tomlinson
2002-10-04 22:21     ` Valdis.Kletnieks
2002-10-04 22:00   ` Andreas Dilger
2002-10-04 22:01 ` Re: [STUPID TESTCASE] " Andreas Dilger
2002-10-07  8:51   ` Oleg Drokin
2002-10-07 13:12   ` Chris Mason
2002-10-08 20:31     ` Manuel Krause
2002-10-04 22:27 ` Hans Reiser [this message]

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=3D9E15C8.2060005@namesys.com \
    --to=reiser@namesys.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=i@stingr.net \
    --cc=manuel.krause@mb.tu-ilmenau.de \
    --cc=mason@suse.com \
    --cc=reiserfs-list@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 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.