From: Nick Piggin <piggin@cyberone.com.au>
To: rwhron@earthlink.net
Cc: akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: i/o benchmarks on 2.5.70* kernels
Date: Tue, 17 Jun 2003 16:27:06 +1000 [thread overview]
Message-ID: <20030617062706.GB6300@didi> (raw)
In-Reply-To: <20030617053232.GA6218@rushmore>
On Tue, Jun 17, 2003 at 01:32:32AM -0400, rwhron@earthlink.net wrote:
> Some benchmarks on 2.5.70* kernels. Hardware is quad P3 xeon
> with 3.75 GB ram. For some workloads, -mm has higher numbers
> than 2.5.70, for others, 2.5.70 is better. Overall, 2.5.70
> seems to give more balanced results on these benchmarks.
>
Thanks.
Recent mm's have had some experimental fair request
allocation code in them which should be sorted now
(not yet in a released mm), and should improve
performance of "queue full" loads such as many
writers or readers.
It might not get the throughput of mainline kernels,
but I have seen 5x better max latency in some cases.
It would be interesting to see how it goes on a big
box.
Don't know whats going on with AIM7, but there have
been a few bugs in AS being fixed.
tiobench on SMP results are not very good, lots of
fragmentation, the random IO throughput drops is
probably due to AS strangling TCQ though. You are
using SMP and TCQ, right?
next prev parent reply other threads:[~2003-06-17 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 5:32 i/o benchmarks on 2.5.70* kernels rwhron
2003-06-17 6:27 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-17 11:14 rwhron
2003-06-18 22:50 rwhron
2003-06-18 23:22 ` Andrew Morton
2003-06-19 8:28 ` Nick Piggin
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=20030617062706.GB6300@didi \
--to=piggin@cyberone.com.au \
--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