All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Dimitrios Apostolou <jimis@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: high system cpu load during intense disk i/o
Date: Tue, 07 Aug 2007 00:12:46 +0200	[thread overview]
Message-ID: <46B79CDE.2030709@interia.pl> (raw)
In-Reply-To: <46B773F6.7060603@gmx.net>

> Hello Rafal,
Hello, 
> However I find it quite possible to have reached the throughput limit 
> because of software (driver) problems. I have done various testing 
> (mostly "hdparm -tT" with exactly the same PC and disks since about 
> kernel 2.6.8 (maybe even earlier). I remember with certainty that read 
> throughput the early days was about 50MB/s for each of the big disks, 
> and combined with RAID 0 I got ~75MB/s. Those figures have been dropping 
> gradually with each new kernel release and the situation today, with 
> 2.6.22, is that hdparm gives maximum throughput 20MB/s for each disk, 
> and for RAID 0 too!
Just tested (plain curiosity).
via82cxxx average result @533MHz:
/dev/hda:
 Timing cached reads:   232 MB in  2.00 seconds = 115.93 MB/sec
 Timing buffered disk reads:   64 MB in  3.12 seconds =  20.54 MB/sec
pata_via average result @533MHz:
/dev/sda:
 Timing cached reads:   234 MB in  2.01 seconds = 116.27 MB/sec
 Timing buffered disk reads:   82 MB in  3.05 seconds =  26.92 MB/sec

Same 2.6.23-rc1-git11 kernel. 
Yes - constant 6MB/s difference (31%). Cool.
> Dimitris
Regards
Rafał

----------------------------------------------------------------------
Jestes sexy? Dodaj swoje fotki i daj sie ocenic na 
>>>http://link.interia.pl/f1b21


  parent reply	other threads:[~2007-08-06 22:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 16:03 high system cpu load during intense disk i/o Dimitrios Apostolou
2007-08-05 16:03 ` Dimitrios Apostolou
2007-08-05 17:58   ` Rafał Bilski
2007-08-05 18:42     ` Dimitrios Apostolou
2007-08-05 20:08       ` Rafał Bilski
2007-08-06 16:14       ` Rafał Bilski
2007-08-06 19:18         ` Dimitrios Apostolou
2007-08-06 19:48           ` Alan Cox
2007-08-07  0:40             ` Dimitrios Apostolou
2007-08-07  0:37               ` Alan Cox
2007-08-07 13:15                 ` Dimitrios Apostolou
2007-08-06 22:12           ` Rafał Bilski [this message]
2007-08-07  0:49             ` Dimitrios Apostolou
2007-08-07  9:03               ` Rafał Bilski
2007-08-07  9:43                 ` Dimitrios Apostolou
2007-08-06  1:28   ` Andrew Morton
2007-08-06 14:20     ` Dimitrios Apostolou
2007-08-06 17:33       ` Andrew Morton
2007-08-06 19:27         ` Dimitrios Apostolou
2007-08-06 20:04         ` Dimitrios Apostolou
2007-08-06 16:09     ` Dimitrios Apostolou
2007-08-07 14:50 ` Dimitrios Apostolou
2007-08-08 19:08   ` Rafał Bilski
2007-08-09  8:17     ` Dimitrios Apostolou
2007-08-10  7:06       ` Rafał Bilski
2007-08-17 23:19         ` Dimitrios Apostolou

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=46B79CDE.2030709@interia.pl \
    --to=rafalbilski@interia.pl \
    --cc=jimis@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.