public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@lycos.it>
To: William Lee Irwin III <wli@holomorphy.com>,
	Ed Sweetman <ed.sweetman@wmich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-rc1
Date: Thu, 1 Jan 2004 19:12:04 +0100	[thread overview]
Message-ID: <200401011912.04358.ornati@lycos.it> (raw)
In-Reply-To: <200312311434.17036.ornati@lycos.it>

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

On Wednesday 31 December 2003 14:34, Paolo Ornati wrote:
>
> With 2.6.1-rc1 I have noticed a strange IDE performance change.
>
> Results of "hdparm -t /dev/hda" with 2.6.0 kernel:
> (readahead = 256):		~26.31 MB/s
> (readahead = 128):		~31.82 MB/s
>
> PS = readahead is set to 256 by default on my system, 128 seems to be the
> best value
>
> Results of "hdparm -t /dev/hda" with 2.6.1-rc1 kernel:
> (readahead = 256):		~26.41 MB/s
> (readahead = 128):		~26.27 MB/s
>
....

I have done new interesting tests.

SCRIPT
___________________________________________________________
#!/bin/bash

echo "HD test for linux `uname -r`"
echo

MIN=32
MAX=512

ra=$MIN
while test $ra -le $MAX; do
    hdparm -a $ra /dev/hda > /dev/null;
    echo -n $ra$'\t';
    s1=`hdparm -t /dev/hda | grep 'Timing' | cut -d'=' -f2| cut -d' ' -f2`;
    s2=`hdparm -t /dev/hda | grep 'Timing' | cut -d'=' -f2| cut -d' ' -f2`;
    s=`echo "scale=2; ($s1+$s2)/2" | bc`;
    echo $s;
    ra=$(($ra+32));
done
___________________________________________________________


o Results for 2.6.0 (first column = readahead, second column = MB/s)

HD test for linux 2.6.0

32	13.78
64	31.74
96	31.77
128	31.74
160	31.84
192	31.87
224	31.21
256	26.31
288	21.75
320	27.22
352	27.46
384	31.63
416	28.15
448	28.25
480	31.54
512	26.24


o Results for 2.6.1-rc1

HD test for linux 2.6.1-rc1

32	26.20
64	26.26
96	26.99
128	26.29
160	26.28
192	25.89
224	26.55
256	26.46
288	30.86
320	26.74
352	26.15
384	25.86
416	26.42
448	26.46
480	26.82
512	26.46


A graphic is attached (red = 2.6.0 / green = 2.6.1-rc1 ;)


BYE

-- 
	Paolo Ornati
	Linux v2.4.23



[-- Attachment #2: ide-hd.png --]
[-- Type: image/png, Size: 5246 bytes --]

  parent reply	other threads:[~2004-01-01 18:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31  8:36 2.6.1-rc1 Linus Torvalds
2003-12-31  8:47 ` 2.6.1-rc1 Mike Fedyk
2003-12-31 10:05 ` 2.6.1-rc1 Tomas Szepe
2003-12-31 12:12   ` 2.6.1-rc1 Jeff Garzik
2003-12-31 15:00 ` 2.6.1-rc1 [resend] Paolo Ornati
2003-12-31 15:06   ` William Lee Irwin III
2003-12-31 15:19     ` Paolo Ornati
2003-12-31 15:20       ` William Lee Irwin III
2003-12-31 15:45         ` Paolo Ornati
2003-12-31 16:31           ` Ed Sweetman
2003-12-31 18:03             ` Paolo Ornati
2004-01-01  9:12   ` 2.6.1-rc1 Andreas Unterkircher
2004-01-01 18:12   ` Paolo Ornati [this message]
2004-01-02  4:51 ` 2.6.1-rc1 with JP106 keyboard Go Taniguchi
2004-01-02  5:46   ` Go Taniguchi
2004-01-02 13:20     ` Vojtech Pavlik
2004-01-02 13:17   ` Vojtech Pavlik
2004-01-02 19:01     ` Go Taniguchi
2004-01-02 20:10       ` Vojtech Pavlik
2004-01-03  5:54         ` Go Taniguchi
2004-01-06 18:33 ` 2.6.1-rc1: SCSI: `TIMEOUT' redefined Adrian Bunk
2004-01-06 22:40   ` [PATCH] " Patrick Mansfield
2004-01-06 22:40   ` Andrew Morton

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=200401011912.04358.ornati@lycos.it \
    --to=ornati@lycos.it \
    --cc=ed.sweetman@wmich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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