From: Cliff White <cliffw@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: [OSDL] - reaim results graphed 2.6.11-rc1
Date: Thu, 20 Jan 2005 09:52:07 -0800 [thread overview]
Message-ID: <200501201752.j0KHq7a04712@mail.osdl.org> (raw)
graphs comparing 2.6.11-rc1 to 2.6.9:
http://developer.osdl.org/cliffw/reaim/compares/2.6.9vs11-rc1/
.html files are named:
<workload>_<filesystem>_<number of cpus>.html
Only notworthy event is apparent regression in reiserfs performance
using the fileserever workload:
http://developer.osdl.org/cliffw/reaim/compares/2.6.9vs11-rc1/new_fserver_reiserfs_2.html
graphs comparing 2.6.11-rc1 to 2.6.10:
http://developer.osdl.org/cliffw/reaim/compares/2.6.10vs11-rc1/
Reisefs regression vs 2.6.10:
http://developer.osdl.org/cliffw/reaim/compares/2.6.10vs11-rc1/new_fserver_reiserfs_2.html
XFS performance also declined. slightly:
http://developer.osdl.org/cliffw/reaim/compares/2.6.10vs11-rc1/new_fserver_xfs_2.html
---------------
cliffw
reply other threads:[~2005-01-20 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200501201752.j0KHq7a04712@mail.osdl.org \
--to=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).