From: Ken Moffat <ken@kenmoffat.uklinux.net>
To: linux-kernel@vger.kernel.org
Subject: IDE throughput in 2.6 - it's good!
Date: Fri, 23 Apr 2004 22:56:41 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.58.0404232237140.19797@ppg_penguin> (raw)
Talk about lies, damned lies, and statistics. I've seen comments about
disk throughput, and running hdparm -t is one of my normal tests for new
kernels. On this particular box (1000Mhz Duron, 512MB) hdparm regularly
reported disk reads of >= 40MB/S, at least on the outside. Then I
booted 2.6.5 and the reported speed dropped away to typically 26-28MB/S.
I remembered a recent comment about block sizes, so I tested the read
speed shown for various partitions. The outer part of the disk has
several VFAT partitions, the ext3 partitions on the inside now report
around 31MB/S - better than 26, but sounds poor, and 2.6.1 reported a
slightly faster speed (might be the compiler, for 2.6.1 I used
gcc-2.95.3, now I'm using gcc-3.3.3). All of the 2.6 kernels on this
box have preempt enabled.
But, when all's said and done these are only numbers. I found the
biggest tar on this box (463MiB) and timed -
cp from hda10 to hda9 (these are the innermost partitions)
sync
rm from hda9
sync again
Repeated three times, no other users, noted the real time.
Under 2.4.25, between 41 and 45 seconds.
Under 2.6.1, between 42 and 50 seconds.
Under 2.6.5, between 38 and 40 seconds.
So, despite the numbers shown by hdparm looking worse, when only one
user is doing anything the performance is actually improved. I've no
idea which changes have achieved this, but thanks to whoever were
involved.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next reply other threads:[~2004-04-23 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 21:56 Ken Moffat [this message]
2004-04-27 15:38 ` Timothy Miller
2004-04-27 19:17 ` Ken Moffat
2004-04-27 20:43 ` Timothy Miller
2004-04-24 15:29 FabF
2004-04-24 23:58 ` IDE " 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=Pine.LNX.4.58.0404232237140.19797@ppg_penguin \
--to=ken@kenmoffat.uklinux.net \
--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®