From: Nick Piggin <piggin@cyberone.com.au>
To: rwhron@earthlink.net
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>,
Joel Becker <Joel.Becker@oracle.com>
Subject: Re: [BENCHMARK] AIM7 fserver regressed in 2.5.70*
Date: Thu, 05 Jun 2003 15:00:22 +1000 [thread overview]
Message-ID: <3EDECE66.8040508@cyberone.com.au> (raw)
In-Reply-To: <20030605024940.GA14406@rushmore>
rwhron@earthlink.net wrote:
>Summary:
>AIM7 fileserver workload behaviour changed with 2.5.70.
>At low task counts (load average), 2.5.70* takes 40%
>longer than 2.5.69. As task count increases, regression
>disappears.
>
>Hardware has (4) 700 mhz P3 Xeons.
>3.75 GB RAM
>RAID 0 LUN (hardware raid)
>
>Background:
>AIM7 fserver is the only regressed workload. In general,
>2.5.70* has better numbers than 2.5.69* for a variety of
>benchmarks.
>
>
[snip]
>AIM7 fserver workload
>kernel Tasks Jobs/Min Real CPU
>2.5.69 4 120.9 200.5 32.8
>2.5.69-bk1 4 122.3 198.2 33.8
>2.5.69-mm3 4 122.3 198.3 37.9
>2.5.69-mm5 4 124.0 195.5 38.0
>
^^^^^^
I think this was the last kernel Joel tested before a
similar magnitude dropoff in WimMark performance.
>
>2.5.70 4 79.0 306.9 34.2
>2.5.70-mjb1 4 83.4 290.8 33.6
>2.5.70-mm3 4 71.7 338.0 34.9
>2.5.70-mm4 4 73.9 328.0 33.9
>
>
I don't know what sort of disk IO fserver does, but it
could be the same problem.
next prev parent reply other threads:[~2003-06-05 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 2:49 [BENCHMARK] AIM7 fserver regressed in 2.5.70* rwhron
2003-06-05 3:35 ` Andrew Morton
2003-06-05 5:00 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-05 10:47 rwhron
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=3EDECE66.8040508@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=Joel.Becker@oracle.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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