From: dth@ncc1701.cistron.net (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Re: harddisk speed: 2.4.24 20+% faster then 2.6.3
Date: Fri, 27 Feb 2004 20:32:28 +0000 (UTC) [thread overview]
Message-ID: <c1o9gs$imc$1@news.cistron.nl> (raw)
In-Reply-To: <20040227200459.GO3925@squish.home.loc>
Paul <set@pobox.com> wrote:
>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
Allready thought about that, tried that but no real
difference:belfish:~# uname -a
Linux babelfish 2.6.3-mm4 #3 Fri Feb 27 14:09:38 CET 2004 i686 GNU/Linux
babelfish:~# /sbin/hdparm -a 4096 /dev/hda
/dev/hda:
setting fs readahead to 4096
readahead = 4096 (on)
babelfish:~# hdparm -t /dev/hda
Timing buffered disk reads: 110 MB in 3.02 seconds = 36.47 MB/sec
I just installed a news amd64 en few 19" servers.
But none of them showed downgrade in performance when i upped the
kernel.
Possibilities left (according to me!)
- scheduler (should i try different setup ?)
- irq problems (in combination with acpi?)
i booted with acpi=off and retested but same results.
- driver, specific the via-onboard.
No luck so far!
Danny
--
/"\ | Dying is to be avoided because
\ / ASCII RIBBON CAMPAIGN | it can ruin your whole career
X against HTML MAIL |
/ \ and POSTINGS | - Bob Hope
prev parent reply other threads:[~2004-02-27 20:32 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
2004-02-27 20:32 ` Danny ter Haar [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='c1o9gs$imc$1@news.cistron.nl' \
--to=dth@ncc1701.cistron.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®