All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Andrea Gelmini <dislessico@gmail.com>,
	ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Linux Gazette benchmark Reiser 4
Date: Mon, 09 Jan 2006 10:22:16 -0800	[thread overview]
Message-ID: <43C2A9D8.80103@namesys.com> (raw)
In-Reply-To: <13dbb67f0601070441q559b156ep@mail.gmail.com>

Andrea Gelmini wrote:

>
>
> 2006/1/6, Robert Hulme <rob@robhulme.com <mailto:rob@robhulme.com>>:
>
>     http://linuxgazette.net/122/TWDT.html#piszcz
>
>     It seems to come off fairly badly in most of the tests.
>
>
> I really did not understand  this kind of benchmark. I don't care
> which filesystem is faster creating 10.000 files (something I never
> have to do). I care about which filesystem fits better with my
> everyday use of my data.
> Days ago I wrote a few script trying to simulate a tipical desktop
> session, *my* tipical desktop session. With different filesystem I've
> got difference of minutes. That's a benchmark that mean something to me.
> Why I'm trying/looking at reiser4?
> Because:
> a) seeks are the real problem of hd (they kill performance);
> b) journal in a fixed position creates a lot of seeks;
> c) I love ext2, but my laptop crash a lot of time in a day (tests,
> battery and so on).
>
> Testing reiser4 is giving to me a good feeling with wondering logs.
> You know... less seek, less HD stress... so more responsiveness.
> Well, it's too early to express an opinion about R4 (I'm using it
> since last week), but the only way to test a FS is to use it for a
> long time.
>
> Sorry for my bad english,
> gelma
>
reiser4 is normally very fast in creating 10,000 files.  I suspect that
there was simply error in how he did the test, and when the guys get
back i will have someone try to reproduce his results.

Justin made so many errors, I  suspect he got something wrong here also.

I encourage you guys to run your own tests, and you will see that we do
fairly well I think.  Advice when benchmarking is:

make sure your fileset is much larger than RAM

make sure the benchmark takes a while to run

create your tarballs on the same fs you use them to benchmark (readdir
order matters)

Assume a 3% noise level.

  parent reply	other threads:[~2006-01-09 18:22 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
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 [this message]
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=43C2A9D8.80103@namesys.com \
    --to=reiser@namesys.com \
    --cc=dislessico@gmail.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.