From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 3094] POOR I/O perfomance on VIA chipsets
Date: Wed, 19 May 2010 17:18:04 GMT [thread overview]
Message-ID: <201005191718.o4JHI4Wa019953@demeter.kernel.org> (raw)
In-Reply-To: <bug-3094-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=3094
--- Comment #21 from Artem S. Tashkinov <t.artem@mailcity.com> 2010-05-19 17:17:37 ---
(In reply to comment #20)
> I/O wait is measuring the amount of time the machine is waiting for the disk,
> not how much it is using CPU. Disks haven't gotten much faster in the past ten
> years (SSD aside) while processors dramatically did. There isn't a lot that can
> be done about the speed of disks,. Getting the kernel to schedule I/O better
> can help a bit but the fundamental problem is that a disk on a good day can
> only really do about 200 operations/second.
What really enrages people (and me too) is that under all circumstances CPU
usage shown by `top` is always 100% whenever a single process is writing or
reading to a spinning storage at full speed.
It is _wrong_ and it is _misleading_ because then people think that the Linux
kernel sucks at I/O operations, everyone instantly recollects Windows
experience where (e.g. on my own PC) HDD access causes maximum 2% CPU usage.
Fix the kernel idle time computation, otherwise people will keep complaining
indefinitely.
`cat /dev/sda > /dev/null` results in load average rapidly climbing to 1.32 and
counting on my PC, that's just insane and wrong.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-05-19 17:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-3094-11633@https.bugzilla.kernel.org/>
2010-05-18 23:33 ` [Bug 3094] POOR I/O perfomance on VIA chipsets bugzilla-daemon
2010-05-18 23:38 ` bugzilla-daemon
2010-05-18 23:44 ` bugzilla-daemon
2010-05-19 0:47 ` bugzilla-daemon
2010-05-19 0:51 ` bugzilla-daemon
2010-05-19 0:59 ` bugzilla-daemon
2010-05-19 1:12 ` bugzilla-daemon
2010-05-19 1:14 ` bugzilla-daemon
2010-05-19 3:08 ` bugzilla-daemon
2010-05-19 6:29 ` bugzilla-daemon
2010-05-19 11:16 ` bugzilla-daemon
2010-05-19 17:18 ` bugzilla-daemon [this message]
2010-05-19 20:53 ` bugzilla-daemon
2010-05-19 23:11 ` bugzilla-daemon
2010-05-20 5:28 ` bugzilla-daemon
2010-05-20 9:09 ` bugzilla-daemon
2010-05-20 15:49 ` bugzilla-daemon
2010-05-20 16:14 ` bugzilla-daemon
2010-05-20 16:56 ` bugzilla-daemon
2010-05-20 17:07 ` bugzilla-daemon
2010-05-20 17:43 ` bugzilla-daemon
2010-05-20 18:51 ` bugzilla-daemon
2010-05-20 19:02 ` bugzilla-daemon
2010-05-20 23:45 ` bugzilla-daemon
2010-05-21 5:48 ` bugzilla-daemon
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=201005191718.o4JHI4Wa019953@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@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.