From: Con Kolivas <conman@kolivas.net>
To: Hans Reiser <reiser@namesys.com>, Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Zarochentcev <zam@namesys.com>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: [BENCHMARK] ext3, reiser, jfs, xfs effect on contest
Date: Sat, 1 Feb 2003 10:18:37 +1100 [thread overview]
Message-ID: <200302011018.37151.conman@kolivas.net> (raw)
In-Reply-To: <200302010921.59861.conman@kolivas.net>
On Saturday 01 Feb 2003 9:21 am, Con Kolivas wrote:
> Actually the most "felt" of these loads is io_load and based on these
> results: io_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2559ext3 3 109 68.8 4 10.1 1.40
> 2559jfs 3 138 54.3 11 13.8 1.77
> 2559reiser 3 98 76.5 2 9.2 1.24
> 2559xfs 3 124 60.5 6 8.0 1.57
>
Here is a set of dbench_load results:
dbench_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2559ext3 3 115 65.2 3 24.3 1.47
2559jfs 3 123 61.8 3 19.5 1.58
2559reiser 3 108 69.4 3 13.9 1.37
2559xfs 3 118 63.6 3 22.0 1.49
Note the order correlates with the order of the io_load results.
Once again reiserfs held up kernel compilation the least. Note they all
accomplished the same work in that time though.
Con
next prev parent reply other threads:[~2003-01-31 23:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 13:20 [BENCHMARK] ext3, reiser, jfs, xfs effect on contest Con Kolivas
2003-01-31 13:37 ` Hans Reiser
2003-01-31 13:40 ` Con Kolivas
2003-01-31 13:56 ` Hans Reiser
2003-01-31 14:15 ` Con Kolivas
2003-01-31 15:21 ` Dave Jones
2003-01-31 16:40 ` Hans Reiser
2003-01-31 16:47 ` Dave Jones
2003-01-31 17:11 ` Hans Reiser
2003-01-31 19:04 ` Andrew Morton
2003-01-31 19:29 ` Hans Reiser
2003-01-31 22:21 ` Con Kolivas
2003-01-31 23:18 ` Con Kolivas [this message]
2003-02-01 0:19 ` David Lang
2003-01-31 14:09 ` Mike A. Harris
2003-01-31 14:18 ` Con Kolivas
2003-01-31 15:00 ` Maciej Soltysiak
2003-02-01 0:12 ` Con Kolivas
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=200302011018.37151.conman@kolivas.net \
--to=conman@kolivas.net \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox