From: Jason Lunz <j@trellisinc.com>
To: Frank de Lange <lkml-frank@unternet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Abysmal interactive performance on 2.4.linus
Date: Mon, 12 Nov 2001 18:28:11 -0500 [thread overview]
Message-ID: <20011112182811.A5412@trellisinc.com> (raw)
In-Reply-To: <20011112205551.A14132@unternet.org> <3BF02BA4.D7E2D70E@mandrakesoft.com> <3BF02BA4.D7E2D70E@mandrakesoft.com> <20011112235642.A17544@unternet.org>
In-Reply-To: <20011112235642.A17544@unternet.org>
In mlist.linux-kernel, you wrote:
> Seems that reiserfs is the common factor here, at least on my box. This is a 35
> GB reiserfs filesystem, app 80% used, both large and small files.
>
> As said in my previous message, the numbers themselves don't mean squat. It is
> the large delays (the fact that user+sys <<< real) which are the problem here.
As another data point, I'm seeing the exact same thing. I haven't tried
any non-Linus kernels, though. But recent 2.4.x (x >= 10?) linus kernels
with reiserfs have these several-second delays during moderate-to-heavy
disk i/o, exactly as you've described. I've seen this on both an SMP
PIII system and a UP Athlon.
--
Jason Lunz Trellis Network Security
j@trellisinc.com http://www.trellisinc.com/
next prev parent reply other threads:[~2001-11-12 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 19:55 Abysmal interactive performance on 2.4.linus Frank de Lange
2001-11-12 20:05 ` Jeff Garzik
2001-11-12 22:22 ` mike@morpheus
2001-11-12 22:56 ` Frank de Lange
2001-11-12 23:21 ` Mike Fedyk
2001-11-12 23:27 ` Martin Josefsson
2001-11-12 23:42 ` Mike Fedyk
2001-11-12 23:28 ` Jason Lunz [this message]
2001-11-13 6:45 ` Oktay Akbal
2001-11-21 8:51 ` Hans Reiser
2001-11-21 9:12 ` Frank de Lange
2001-11-21 12:49 ` Yury Yu. Rupasov
2001-11-12 20:06 ` Martin Josefsson
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 21:16 Frank de Lange
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=20011112182811.A5412@trellisinc.com \
--to=j@trellisinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml-frank@unternet.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