All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Cliff White <cliffw@osdl.org>
Cc: Andrew Morton <akpm@digeo.com>,
	Paolo Ciarrocchi <ciarrocchi@linuxmail.org>,
	linux-kernel@vger.kernel.org, Chris Mason <mason@suse.com>
Subject: Re: [Benchmark] AIM9 results
Date: Mon, 23 Dec 2002 10:13:34 +0300	[thread overview]
Message-ID: <3E06B79E.8030903@namesys.com> (raw)
In-Reply-To: <200212181847.gBIIlhO26530@mail.osdl.org>

Cliff White wrote:

>>Andrew Morton wrote:
>>
>>    
>>
>>>Andrew Morton wrote:
>>> 
>>>
>>>      
>>>
>>>>Hans Reiser wrote:
>>>>   
>>>>
>>>>        
>>>>
>>>>>Andrew and Chris, are these changes in performance definitely due to VM
>>>>>changes (and not some difference I am not thinking of between 2.5 and
>>>>>2.4 reiserfs code)?
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>aim9 is just doing
>>>>
>>>>       for (lots)
>>>>               close(creat(filename))
>>>>   
>>>>
>>>>        
>>>>
>>>                 unlink(filename);	/* of course */
>>>
>>>
>>> 
>>>
>>>      
>>>
>>Oh, commercial fs vendors must really love tuning for this benchmark.... 
>>sigh....
>>
>>    
>>
>Ya, we think the AIM stuff is getting a little old. The basic idea is fine, but
>many of the tests do _very little work.  We (OSDL) would like to re-do 
>AIM9+7 and make it more useful. We'd love to have some input from everyone....
>For example, how big a file should we create for a real creat() test ?
>cliffw
>
>  
>
>  
>
Well, if you take a look at mongo.pl available at www.namesys.com we 
provide you with a fractal file size generation program that you might 
want to look at, that mongo uses during the creation portion of its 
benchmark.

It makes 80% of the files less than some amount (100 bytes, or 1k, or 
4k, depending on how mean you want to be to ext2;-) ), then 80% of the 
remaining 20% less than 10 times that amount then....

There is more than one version of the file size generation code, so make 
sure you got the one that works as I described above.  I am looking for 
a formula to smooth the above behavior into some sort of gentle curve 
rather than sharp bands, but I haven't found it yet.

Hans


  parent reply	other threads:[~2002-12-23  7:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 22:52 [Benchmark] AIM9 results Paolo Ciarrocchi
2002-12-16 23:09 ` Hans Reiser
2002-12-16 23:25   ` Andrew Morton
2002-12-16 23:37     ` Andrew Morton
2002-12-17  0:00       ` Hans Reiser
2002-12-18 18:47         ` Cliff White
2002-12-18 19:10           ` Nikita Danilov
2002-12-23  7:13           ` Hans Reiser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-10 22:10 [BENCHMARK] " Paolo Ciarrocchi
2002-11-28 13:41 [Benchmark] " Paolo Ciarrocchi
     [not found] <r1_20021126213149.29517.qmail@linuxmail.org>
2002-11-28 13:18 ` Bill Davidsen
2002-11-27 22:55 Paolo Ciarrocchi
2002-11-26 21:31 Paolo Ciarrocchi

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=3E06B79E.8030903@namesys.com \
    --to=reiser@namesys.com \
    --cc=akpm@digeo.com \
    --cc=ciarrocchi@linuxmail.org \
    --cc=cliffw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.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.