From: Andrew Morton <akpm@digeo.com>
To: Siva Koti Reddy <siva.kotireddy@wipro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCH MARK] 'tiobench' results comparision for 2.5.43 kernel and 2.4.19
Date: Wed, 16 Oct 2002 09:37:33 -0700 [thread overview]
Message-ID: <3DAD95CD.DB7F8C26@digeo.com> (raw)
In-Reply-To: 04fd01c2750d$c895a470$690b720a@M3104487
Siva Koti Reddy wrote:
>
> Hai...
> Here is the benchmark results of tiobench for 2.5.43 kernel and 2.4.19
> kernel. There is a drastic performance degradation in Read operations of
> 2.5.43 kernel as compared to 2.4.19 kernel though there is a little
> improvement in write operations. Any cooments..?
>
The tiobench threaded read phase is very sensitive to the
interworking between readahead and the disk scheduler. 2.4
gets this right, and 2.5 does not.
2.5 seeks between the files with a granularity equal to the
readahead window size. 2.4 seeks betwen the files at a
granularity equal to the elevator request expiry count.
So yup, it's known. Haven't investigated it yet.
prev parent reply other threads:[~2002-10-16 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 12:15 [BENCH MARK] 'tiobench' results comparision for 2.5.43 kernel and 2.4.19 Siva Koti Reddy
2002-10-16 16:37 ` Andrew Morton [this message]
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=3DAD95CD.DB7F8C26@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=siva.kotireddy@wipro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox