From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Helge Hafting <helgehaf@idb.hist.no>
Cc: jlm <jsado@mediaone.net>, Andre Hedrick <andre@linuxdiskcert.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Poor performance during disk writes
Date: Thu, 20 Dec 2001 14:27:17 +0100 [thread overview]
Message-ID: <20011220132729Z286241-18285+3296@vger.kernel.org> (raw)
On Thursday, 20.12.201, 10:49 Helge Hafting wrote:
> jlm wrote:
[-]
> > So I guess I don't really care what mode the hard drive is operating in
> > (udma, mdma, dma or plain ide), I just don't want to have to go get a
> > cup of coffee while the hard drive saves some data. Is there a "don't
>
> Devices generally get the cpu before anything else. A good disk system
> don't need much cpu. Running IDE in PIO mode require a lot
> of cpu though. Using any of the DMA modes avoids that.
Amen..
Sorry, Helge sure you are right in theory but try dbench 32 (maybe
bonnie/bonnie++) and playing an MP3/Ogg-Vorbis in parallel...
That's my first test on any "new" kernel version.
Even with an 1 GHz Athlon II, 640 MB, U160 DDYS 18 GB, 10k IBM disk (on an
AHA-2940UW) it stutters like mad. I am running all my kernel _with_ Robert
Love's preempt + lock-break patches and it doesn't solve the problem.
CPU load is (very) low but it do not work like it should.
> > pre-empt the rest of the system" switch for the eide drives? Is there
> > something fundamental/unique going on here that I'm missing?
> dma, udma, etc. is that switch. It lets the cpu do other work (such as
> redrawing X) while the disk is busy. Plain ide is what you don't want.
See above the whole system show some bad hiccup.
> The problem of waiting for other files or swapping while a really big
> write is going on is different. Get more drives, so the big writes go
> to one drive while you get stuff swapped in (or other file access)
> on other drive(s). The kernel is capable of getting fast response
> from one drive while another is completely bogged down with
> enormous writes.
Tried this already. Neither I put my test files (MP3/Ogg-Vorbis) in /dev/shm
or a nother disk it do not change anything.
There must be something in the VFS?
-Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
@home: Dieter.Nuetzel@hamburg.de
next reply other threads:[~2001-12-20 13:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 13:27 Dieter Nützel [this message]
2001-12-20 14:51 ` Poor performance during disk writes safemode
2001-12-20 17:40 ` William Lee Irwin III
2001-12-20 18:19 ` Andrew Morton
2001-12-20 18:29 ` Dave Jones
2001-12-21 16:50 ` Jens Axboe
2001-12-21 16:50 ` Jens Axboe
[not found] ` <0112201629230E.01835@manta>
[not found] ` <200112201436.fBKEa2m26640@zero.tech9.net>
2001-12-20 19:02 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-12-18 0:53 jlm
2001-12-18 1:09 ` Reid Hekman
2001-12-18 1:36 ` jlm
2001-12-18 2:01 ` Reid Hekman
2001-12-18 18:46 ` Andre Hedrick
2001-12-18 17:42 ` Gérard Roudier
2001-12-18 20:34 ` Andre Hedrick
2001-12-18 19:09 ` Gérard Roudier
2001-12-19 23:26 ` jlm
2001-12-20 10:49 ` Helge Hafting
2001-12-21 16:29 ` Troy Benjegerdes
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=20011220132729Z286241-18285+3296@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=andre@linuxdiskcert.org \
--cc=helgehaf@idb.hist.no \
--cc=jsado@mediaone.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