From: Mike Fedyk <mfedyk@matchmail.com>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Alex Bennee <kernel-hacker@bennee.com>,
Rik van Riel <riel@redhat.com>,
Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x: iowait problem while burning a CD
Date: Sun, 29 Feb 2004 02:35:12 -0800 [thread overview]
Message-ID: <4041C060.8090704@matchmail.com> (raw)
In-Reply-To: <200402291027.34655.ornati@fastwebnet.it>
Paolo Ornati wrote:
> On Saturday 28 February 2004 15:52, Alex Bennee wrote:
>
>>>>At that point, mkisofs is probably running into a bazillion
>>>>small files, in subdirectories all over the place.
>>>>
>>>>Because a disk seek + track read takes 10ms, it's simply not
>>>>possible to read more than maybe 100 of these small files a
>>>>second, so mkisofs can't keep up.
>>>
>>>No... mkfs is reading only ONE big file ( ~ 700 MB )!
>>>
>>>And my system shouldn't be so slow:
>>>
>>>CPU: AMD Duron 750
>>>RAM: 128 MB PC100
>>>HD: 7200 RPM udma 4
>>>File System: ResiserFS
>>
>>Could this be related to your low(ish) physical memory and the need swap
>>stuff in and out? Maybe you could look at the vmstat output as you run
>>the two cases?
>
>
> No... swap is never touched !
>
> But I think to have found where the problem is:
>
> if I only create an ISO image of 672.4 MB I must wait more then 5 minutes...
> this means about 2.2 MB/s !
How full is your filesystem on average? If it has been around 90% or
more, you might be having trouble with fragmentation.
next prev parent reply other threads:[~2004-02-29 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 17:02 2.6.x: iowait problem while burning a CD Paolo Ornati
2004-02-28 0:18 ` Rik van Riel
2004-02-28 9:14 ` Paolo Ornati
2004-02-28 14:52 ` Alex Bennee
2004-02-29 9:27 ` Paolo Ornati
2004-02-29 10:35 ` Mike Fedyk [this message]
2004-02-29 13:38 ` 2.6.x: iowait problem while burning a CD: SOLVED Paolo Ornati
2004-02-28 22:39 ` 2.6.x: iowait problem while burning a CD Bill Davidsen
2004-02-29 9:37 ` Paolo Ornati
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=4041C060.8090704@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=kernel-hacker@bennee.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
--cc=riel@redhat.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 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.