All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Brian Tinsley <btinsley@emageon.com>
Cc: ReiserFS <reiserfs-list@namesys.com>
Subject: Re: what do you do that stresses your filesystem?
Date: Sun, 05 Jan 2003 11:17:05 +0300	[thread overview]
Message-ID: <3E17EA01.1080309@namesys.com> (raw)
In-Reply-To: <3E0D364F.1010008@emageon.com>

Brian Tinsley wrote:

> I'm late replying to this one, but I've been on vacation :)
>
> Any possible optimizations for the following would be beneficial:
>  * interaction with the Linux NFS server 

Yes, agreed, especially 0 copy stuff.

>
>  * SMP machines 

already addressed by reiser4 (but not tested and benchmarked yet)

>
>  * apps like grep, awk, and sed 

reasonable.

>
>
> Any optimizations for the following application characteristics would 
> be beneficial:
>
>  * Our applications perform multi-threaded streaming I/O 
> (network-to-disk and vice versa) with read/write block sizes varying 
> from 16KB to 64KB; we have files ranging in size from 32KB to 500MB+ 
> (this top end will likely grow into several GB in the near future). 

hopefully allocate on flush will optimize that well enough.  how many 
threads?

>
>  * Our directory structure is very broad, but not very deep and files 
> are stored in leaf nodes only. 

hopefully reiserfs already does this one well.

>
>  * When a file is created and completely written to disk, it is often 
> re-read in its entirety at least two times within a couple of minutes. 

Hopefully current lru algorithms handle this.

>
>  * Our database app performs lots of block-based random I/O and fsyncs 
> within a dozen or so large files. 

This we have not given a lot of attention to, and probably some serious 
study of it is desirable.  I hope that we do reasonably well at this, 
but I can't say that I know that we do.

Thanks Brian, this was a good list.

>
>
>
>
> Hans Reiser wrote:
>
>> We were discussing how to optimize reiser4 best, and came to realize 
>> that us developers did not have a good enough intuition for what 
>> users do that stresses their filesystem enough that they care about 
>> its performance.
>>
>> If you just do edits of files it probably does not matter too much 
>> what fs you use.
>>
>> Booting the machine seems like one activity that many users end up 
>> waiting on the FS for.  Yes?
>>
>> Starting up complex and big applications like xemacs and mozilla 
>> would be another.  Yes?
>>
>> Others?
>>
>> Hans
>>
>> PS
>>
>> reiser4 performance is up a lot recently, and within two weeks I 
>> think cp -r will have been optimized as much as is worth doing.  cp 
>> -r accesses files in readdir order, and that does indeed seem worth 
>> optimizing, but soon we will need to optimize more sophisticated 
>> access patterns than that.....
>>
>> Hans
>
>
>


-- 
Hans



  reply	other threads:[~2003-01-05  8:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 11:28 what do you do that stresses your filesystem? Hans Reiser
2002-12-23 11:37 ` Anders Widman
2002-12-23 11:45   ` Hans Reiser
2002-12-23 12:36     ` Ed Tomlinson
2002-12-24  9:22       ` Hans Reiser
2002-12-23 22:02   ` Dieter Nützel
2002-12-23 11:49 ` new reiserfs4 snapshots? Ookhoi
2002-12-23 12:03 ` what do you do that stresses your filesystem? Hendrik Visage
2002-12-23 12:10   ` Oleg Drokin
2002-12-23 12:12     ` Hans Reiser
2002-12-23 12:21       ` Hendrik Visage
2002-12-23 12:26         ` Oleg Drokin
2002-12-23 12:37           ` Hendrik Visage
2002-12-23 14:18             ` Oleg Drokin
2002-12-23 14:37       ` Eric Whiting
2002-12-23 13:21 ` Russell Coker
2002-12-23 16:00   ` Alexander G. M. Smith
2002-12-24  9:26   ` Hans Reiser
2002-12-24 10:15     ` Ookhoi
2002-12-24 10:19       ` Oleg Drokin
2002-12-24 10:26         ` Ookhoi
2002-12-24 11:57       ` Hans Reiser
2002-12-24 12:41     ` Russell Coker
2002-12-23 14:44 ` bscott
2002-12-23 15:56 ` Ross Vandegrift
2002-12-23 20:12   ` Russell Coker
2002-12-23 16:33 ` Chris Haynes
2002-12-24  9:36   ` Hans Reiser
2003-01-06 15:14     ` Chris Mason
2002-12-23 18:54 ` Matthew Johnson
2002-12-23 21:04 ` Manuel Krause
2002-12-23 21:14 ` Andrew Clausen
2002-12-28  5:27 ` Brian Tinsley
2003-01-05  8:17   ` Hans Reiser [this message]
2003-01-05 11:49     ` Legato (was: " Hendrik Visage
2003-01-05 17:00       ` Brian Tinsley
2003-01-06  7:00       ` Hans Reiser
2003-01-05 16:51     ` Brian Tinsley
2003-01-06  7:10       ` Hans Reiser
2003-01-05 15:01 ` Philipp Gühring
2003-01-11 15:25 ` Zygo Blaxell

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=3E17EA01.1080309@namesys.com \
    --to=reiser@namesys.com \
    --cc=btinsley@emageon.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.