From: "Massimo Cetra" <mcetra@navynet.it>
To: "'Nick Piggin'" <nickpiggin@yahoo.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Production comparison between 2.4.27 and 2.6.8.1
Date: Sun, 22 Aug 2004 18:54:57 +0200 [thread overview]
Message-ID: <000a01c48868$c1b334e0$0600640a@guendalin> (raw)
In-Reply-To: <4127F7FD.5060804@yahoo.com.au>
Nick Piggin Wrote:
> I wouldn't worry too much about hdparm measurements. If you
> want to test the streaming throughput of the disk, run dd
> if=big-file of=/dev/null or a large write+sync.
>
> Regarding your worse non-RAID XFS database results, try
> booting 2.6 with elevator=deadline and test again. If yes,
> are you using queueing (TCQ) on your disks?
Done another test.
This time I created a 256Mb ramdisk, formatted it as ext3 and mounted as
data partition.
Results are the following:
2.6.8.1:
A)
real 0m0.437s
user 0m0.036s
sys 0m0.013s
B)
real 0m37.307s
user 0m3.212s
sys 0m1.287s
2.4.7:
A)
real 0m0.437s
user 0m0.024s
sys 0m0.010s
B)
real 0m38.180s
user 0m2.950s
sys 0m1.602s
In this case results are comparable.
What is the difference, so?
2.6 performs better reading from disk.
Avoiding PCI, SATA and disks on this test makes 2.4 and 2.6 perform in
the same way.
Hope this helps.
Massimo Cetra
next prev parent reply other threads:[~2004-08-22 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 17:25 Production comparison between 2.4.27 and 2.6.8.1 Massimo Cetra
2004-08-22 1:33 ` Nick Piggin
2004-08-22 15:43 ` Massimo Cetra
2004-08-22 16:54 ` Massimo Cetra [this message]
2004-08-23 11:46 ` Massimo Cetra
2004-08-24 2:05 ` Nick Piggin
2004-08-24 14:15 ` Massimo Cetra
2004-08-25 2:28 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 7:23 rwhron
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='000a01c48868$c1b334e0$0600640a@guendalin' \
--to=mcetra@navynet.it \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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