From: Hans Reiser <reiser@namesys.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Adrian Ulrich <reiser4@blinkenlights.ch>,
reiserfs-list@namesys.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Small ZFS / Reiser4 / Ext 'benchmark'
Date: Thu, 02 Feb 2006 22:14:06 -0800 [thread overview]
Message-ID: <43E2F4AE.6070902@namesys.com> (raw)
In-Reply-To: <20060202225422.GT11642@schatzie.adilger.int>
I am surprised that Reiser4 does so well, and I would be interested in
knowing more details of exactly what the test does. Our tests show
reiser4 not doing THAT much better, so you must be doing something
different from our tests.
I learn from almost every benchmark done by other people, because they
almost always test differently from what I had imagined I should test.
Hans
parent reply other threads:[~2006-02-03 6:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20060202225422.GT11642@schatzie.adilger.int>]
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=43E2F4AE.6070902@namesys.com \
--to=reiser@namesys.com \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser4@blinkenlights.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox