From: Hans Reiser <reiser@namesys.com>
To: Cyrille Chepelov <cyrille@chepelov.org>
Cc: reiserfs-list@namesys.com, vs <vs@thebsh.namesys.com>,
zam@thebsh.namesys.com
Subject: Re: [r4] a few benchmarks
Date: Sun, 17 Aug 2003 20:26:34 +0400 [thread overview]
Message-ID: <3F3FACBA.8020208@namesys.com> (raw)
In-Reply-To: <20030816203028.GA14504@chepelov.org>
Cyrille Chepelov wrote:
>Hi all,
>
>I performed a couple of benchmarks on a spare machine, and put them online.
>
>I couldn't perform all the tests I wanted (see my previous "oops" message),
>the hardware is not exactly representative of today's machines, some details
>would use some tuning for more representative results, and I had
>ideas for extra things I'd like to measure, but here are today's results anyway
>for what it's worth: http://www.chepelov.org/cyrille/fsbench-results
>
> -- Cyrille
>
>
>
One of the key things in reproducing these results may be the 32 meg of ram.
--
Hans
next prev parent reply other threads:[~2003-08-17 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 20:30 [r4] a few benchmarks Cyrille Chepelov
2003-08-17 16:04 ` Hans Reiser
2003-08-17 16:26 ` Hans Reiser [this message]
2003-08-17 21:16 ` Mike Fedyk
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=3F3FACBA.8020208@namesys.com \
--to=reiser@namesys.com \
--cc=cyrille@chepelov.org \
--cc=reiserfs-list@namesys.com \
--cc=vs@thebsh.namesys.com \
--cc=zam@thebsh.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.