From: Hans Reiser <reiser@namesys.com>
To: Ricardo Galli <gallir@uib.es>
Cc: linux-kernel@vger.kernel.org, timothy@monkey.org,
Guillem Cantallops Ramis <guillem@cantallops.net>,
"Yury Yu. Rupasov" <yura@yura.polnet.botik.ru>,
reiserfs-dev@namesys.com
Subject: Re: New XFS, ReiserFS and Ext2 benchmarks
Date: Mon, 21 May 2001 22:12:30 -0700 [thread overview]
Message-ID: <3B09F53E.FE67E795@namesys.com> (raw)
In-Reply-To: <LOEGIBFACGNBNCDJMJMOKEADCJAA.gallir@uib.es>
Ricardo Galli wrote:
>
> Hi,
> you can find at http://bulma.lug.net/static/ a few new benchmarks among
> Reiser, XFS and Ext2 (also one with JFS).
>
> This time there is a comprehensive Hans' Mongo benchmarks
> (http://bulma.lug.net/static/mongo/ )and a couple of kernel compilations and
> read/write/fsync operations tests (I was very careful of populating the
> cache before the measures for the last two cases).
>
> Regards,
>
> --ricardo
> http://m3d.uib.es/~gallir/
These are interesting benchmarks, my only caveats are that make bzImage is
probably CPU bound not IO bound (the traditional value of compiles as FS
benchmarks does not apply to Linux filesystems, as they don't do the misdesigned
synchronization policy of older Unices, and compiles are CPU bound for them in
my experience), that I don't understand fully why we are so much faster at the
cp -ar, and I would like Yura to try to reproduce the cp -ar as it seems too
good to be true.
Thanks for investing the time into this Ricardo.
Hans
next prev parent reply other threads:[~2001-05-22 5:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 2:41 New XFS, ReiserFS and Ext2 benchmarks Ricardo Galli
2001-05-22 5:12 ` Hans Reiser [this message]
2001-05-22 5:54 ` [reiserfs-dev] " Hans Reiser
2001-05-22 9:48 ` Ricardo Galli
2001-05-22 16:16 ` Hans Reiser
2001-05-22 16:45 ` Ricardo Galli
2001-05-22 10:29 ` Daniel Phillips
2001-05-22 14:48 ` Shawn
2001-05-22 15:29 ` Daniel Phillips
2001-05-22 15:36 ` Rik van Riel
2001-05-22 18:20 ` David N. Lombard
2001-05-22 22:19 ` Daniel Phillips
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=3B09F53E.FE67E795@namesys.com \
--to=reiser@namesys.com \
--cc=gallir@uib.es \
--cc=guillem@cantallops.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=timothy@monkey.org \
--cc=yura@yura.polnet.botik.ru \
/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