From: Paul <set@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: harddisk speed: 2.4.24 20+% faster then 2.6.3
Date: Fri, 27 Feb 2004 15:04:59 -0500 [thread overview]
Message-ID: <20040227200459.GO3925@squish.home.loc> (raw)
In-Reply-To: <c1m1id$u31$1@news.cistron.nl>
Danny ter Haar <dth@ncc1701.cistron.net>, on Fri Feb 27, 2004 [12:04:29 AM] said:
> I've been checking, rechecking but cannot explain
> why a "vannilla" debian install kernel (sid-testing install
> cdrom) is faster then "Feisty Dunnart" on the same hardware.
>
> hardware: Mini-itx with 1Ghz via-C3
> 200GB udma harddisk.
>
> 2.4.24:
> Timing buffered disk reads: 150 MB in 3.01 seconds = 49.83 MB/sec
>
> 2.6.3 (vanilla):
> Timing buffered disk reads: 102 MB in 3.05 seconds = 33.40 MB/sec
>
> 2.6.3-mm4:
> Timing buffered disk reads: 108 MB in 3.00 seconds = 35.95 MB/sec
>
Hi;
By default, my hdparm numbers and my kernel build time
benchmark were worse on all 2.6 vs. 2.4 kernels, until I tried:
/sbin/hdparm -a 4096 /dev/hdx
eg. (typical averages)
2.4.21:
Timing buffered disk reads: 80 MB in 3.07 seconds = 26.06 MB/sec
2.6.0-test5:
Timing buffered disk reads: 68 MB in 3.06 seconds = 22.21 MB/sec
2.6.1: [readahead 4096]
Timing buffered disk reads: 90 MB in 3.02 seconds = 29.82 MB/sec
2.6.0-test10 building 2.4.18-packet (personal config) gcc3.2.3 glibc2.3.2
160g Maxtor, ext3
(2xpII 400)
time (make -j4 clean && make -j4 dep && make -j4 bzImage)
[with default read-ahead]
real 9m1.496s
user 16m1.977s
sys 0m45.347s
[read-ahead = 4096]
real 7m2.923s
user 12m6.889s
sys 0m46.190s
pIIx4, ata33, 160g maxtor
Paul
set@pobox.com
next prev parent reply other threads:[~2004-02-27 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 0:04 Danny ter Haar
2004-02-27 20:04 ` Paul [this message]
2004-02-27 20:32 ` Danny ter Haar
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=20040227200459.GO3925@squish.home.loc \
--to=set@pobox.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
all inboxes | Powered by JetHome®