All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Pysiak Satriani <pysiak.satriani@wp.pl>
Cc: Edward Shishkin <edward@namesys.com>, PFC <lists@peufeu.com>,
	jpiszcz@lucidpixels.com, reiserfs-list@namesys.com,
	Alexander Zarochentcev <zam@namesys.com>
Subject: Re: Linux Gazette benchmark Reiser 4
Date: Mon, 09 Jan 2006 11:50:20 -0800	[thread overview]
Message-ID: <43C2BE7C.8010703@namesys.com> (raw)
In-Reply-To: <267316269.20060109120422@wp.pl>

Pysiak Satriani wrote:

>Hello Edward,
>
>Sunday, January 8, 2006, 11:07:46 PM, you wrote:
>  
>
>>Let's consider this important aspect of benchmarking more carefully.
>>So there is an interesting question: how much should be a difference
>>in order to approve that some fs really wins at this statistics? Is
>>there any guarantee you won't get, say, 0.05 and 0.02 after next run?
>>Sorry, but I didn't find any answer in Justin's notes, NOTE5 (Tests
>>Performed) says that questionable tests were re-run, but it seems we
>>need something kinda research here instead of re-run.
>>    
>>
>Exactly. By the way, Justin writes he did only 3 tests and calculated
>the average out of these 3. In statistics this is a very small sample.
>We would need at least 30 or so. If the results would have a big
>variance, they should be treated with exponential smoothening.
>And then we can go off with the calculations. Also It would be nice
>to have data from the exact tests made regularly to test for regressions
>and see what's the trend.
>  
>
I can just tell you from experience that benchmarks that take less than
a minute have a high tendency to be poor measures  He should increase
the size of the benchmark until each thing he measures takes more than 2
minutes.  If it is reproduceable it can be still meaningless.

Hans


  reply	other threads:[~2006-01-09 19:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 18:10 Linux Gazette benchmark Reiser 4 Robert Hulme
2006-01-06 19:09 ` PFC
2006-01-06 20:15   ` Hans Reiser
2006-01-08 22:07     ` Edward Shishkin
2006-01-09 11:04       ` Re[2]: " Pysiak Satriani
2006-01-09 19:50         ` Hans Reiser [this message]
2006-01-10  7:57       ` Hans Reiser
2006-01-07 12:41 ` Andrea Gelmini
2006-01-07 14:03   ` Philippe Gramoullé
2006-01-09 18:22   ` Hans Reiser
2006-01-09 19:01     ` Marcel Hilzinger
2006-01-18  8:28       ` A question: May Reiser4 be equivalent to Reiser3 with some flag/plugin Giovanni A. Orlando
2006-01-18 17:40         ` Hans Reiser
2006-01-18 18:43           ` Giovanni A. Orlando
2006-01-18 18:21         ` Vladimir V. Saveliev
2006-01-18 18:39           ` Giovanni A. Orlando
2006-01-18 20:17         ` Vladimir V. Saveliev

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=43C2BE7C.8010703@namesys.com \
    --to=reiser@namesys.com \
    --cc=edward@namesys.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=lists@peufeu.com \
    --cc=pysiak.satriani@wp.pl \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@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.