From: Alex Riesen <alexander.riesen@synopsys.COM>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WimMark I for 2.5.64-mm1
Date: Fri, 7 Mar 2003 19:06:53 +0100 [thread overview]
Message-ID: <20030307180653.GA30288@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <20030307175700.GA2835@ca-server1.us.oracle.com>
Joel Becker, Fri, Mar 07, 2003 18:57:01 +0100:
>
> WimMark I report for 2.5.64-mm1
>
> Runs with anticipatory scheduler: 547.28 580.69
> Runs with deadline scheduler: 1557.79 1360.52
What do the numbers mean?
Is AS better or worse DS?
> WimMark I is a rough benchmark we have been running
> here at Oracle against various kernels. Each run tests an OLTP
> workload on the Oracle database with somewhat restrictive memory
> conditions. This reduces in-memory buffering of data, allowing for
> more I/O. The I/O is read and sync write, random and seek-laden.
> The benchmark is called "WimMark I" because it has no
> official standing and is only a relative benchmark useful for comparing
> kernel changes. The benchmark is normalized an arbitrary kernel, which
> scores 1000.0. All other numbers are relative to this.
> The machine in question is a 4 way 700 MHz Xeon machine with 2GB
> of RAM. CONFIG_HIGHMEM4GB is selected. The disk accessed for data is a
> 10K RPM U2W SCSI of similar vintage. Unless mentioned, all runs are
> on this machine (variation in hardware would indeed change the
> benchmark).
next prev parent reply other threads:[~2003-03-07 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 17:57 WimMark I for 2.5.64-mm1 Joel Becker
2003-03-07 18:06 ` Alex Riesen [this message]
2003-03-07 19:17 ` Joel Becker
2003-03-07 18:43 ` Andrew Morton
2003-03-07 19:19 ` Joel Becker
2003-03-07 19:28 ` Randy.Dunlap
2003-03-07 19:44 ` Joel Becker
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=20030307180653.GA30288@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=Joel.Becker@oracle.com \
--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