From: Ed Tomlinson <tomlins@cam.org>
To: Chris Mason <mason@suse.com>,
reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] reiserfs patch for 2.4.0-prerelease
Date: Thu, 4 Jan 2001 20:41:13 -0500 [thread overview]
Message-ID: <01010420411300.00624@oscar> (raw)
In-Reply-To: <244070000.978645169@tiny>
In-Reply-To: <244070000.978645169@tiny>
Hi,
I have been doing some dbench runs with the original and latest (Jan 4 22:xx)
prerelease.diff kernels. Looks like both the latest kernels and the reiserfs
patch both are costing some performance.
prerelease
MB/s user system cpu time
ext2 14.6 50.5s 76.4s 29% 7:14.9m
ext2 12.6 50.9s 76.7s 25% 8:23.6m
reiser 14.5 53.8s 149.2s 46% 7:16.1m
reiser 10.7 54.1s 154.5s 35% 9:49.9m
prerelease (2.4.0 jan 4 22:xx)
MB/s user system cpu time
ext2 10.5 52.8s 81.5s 22% 10:02.3m
reiser 5.8 54.6s 198.5s 23% 18:12.5m
reiser 6.4 55.1s 188.7s 24% 16.19.3m
Using the notail reiserfs mount option improves the reiserfs numbers 10-20%
with both kernels.
All benchmarks run on a K6-III 400 with 128M just after boot with no X
running.
Comments?
Ed Tomlinson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-05 1:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 21:52 reiserfs patch for 2.4.0-prerelease Chris Mason
2001-01-05 1:41 ` Ed Tomlinson [this message]
2001-01-06 16:52 ` [reiserfs-list] reiserfs patch for 2.4.0-prerelease (dbench runs) Ed Tomlinson
2001-01-05 13:04 ` reiserfs patch for 2.4.0-final Claas Langbehn
2001-01-05 13:47 ` Chris Mason
2001-01-05 15:56 ` Chris Evans
2001-01-05 16:54 ` Rik van Riel
2001-01-05 17:41 ` Chris Mason
2001-01-05 17:45 ` Admin Mailing Lists
2001-01-05 17:48 ` Rik van Riel
2001-01-05 18:44 ` Alan Cox
2001-01-05 18:52 ` Admin Mailing Lists
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=01010420411300.00624@oscar \
--to=tomlins@cam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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.