From: Frank de Lange <lkml-frank@unternet.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Frank de Lange <lkml-frank@unternet.org>, linux-kernel@vger.kernel.org
Subject: Re: Abysmal interactive performance on 2.4.linus
Date: Mon, 12 Nov 2001 23:56:42 +0100 [thread overview]
Message-ID: <20011112235642.A17544@unternet.org> (raw)
In-Reply-To: <20011112205551.A14132@unternet.org> <3BF02BA4.D7E2D70E@mandrakesoft.com>
In-Reply-To: <3BF02BA4.D7E2D70E@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Mon, Nov 12, 2001 at 03:05:56PM -0500
On Mon, Nov 12, 2001 at 03:05:56PM -0500, Jeff Garzik wrote:
> Can you try 2.4.13ac6 (not 7/8), and 2.2.20, and post a comparison?
Here's the results from some tests I did:
2.2.20
======
without filesystem activity
no slowdowns observed
time ls -al /usr/|sort -k 5 -n
real 0m0.121s
user 0m0.000s
sys 0m0.090s
with filesystem activity on ext2
no slowdowns observed
time ls -al /opt/|sort -k 5 -n
real 0m0.079s
user 0m0.010s
sys 0m0.100s
2.4.13-ac5
==========
no slowdowns observed
without filesystem activity
time ls -al /usr/|sort -k 5 -n
real 0m0.142s
user 0m0.000s
sys 0m0.000s
with filesystem activity on ext2
no slowdowns observed
time ls -al /opt/|sort -k 5 -n
real 0m0.022s
user 0m0.020s
sys 0m0.010s
with filesystem activity on reiserfs
- it took 31 seconds to just open this small ( < 1 kb) text file (which
resides in my home directory, on an ext2 filesystem) in vi...
time ls -al /usr/|sort -k 5 -n
real 0m6.136s
user 0m0.020s
sys 0m0.020s
2.4.15-pre4
===========
without filesystem activity
no slowdowns observed
time ls -al /usr/|sort -k 5 -n
real 0m0.081s
user 0m0.010s
sys 0m0.010s
with filesystem activity on ext2
no slowdowns observed
time ls -al /usr/|sort -k 5 -n
real 0m0.146s
user 0m0.000s
sys 0m0.020s
with filesystem activity on reiserfs
system behaviour erratic, some slowdowns
time ls -al /opt|sort -k5 -n
real 0m13.232s
user 0m0.020s
sys 0m0.010s
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.
Any other magic anyone wants me to perform? Hans, you reading this?
Cheers//Frank
--
WWWWW _______________________
## o o\ / Frank de Lange \
}# \| / \
##---# _/ <Hacker for Hire> \
#### \ +31-320-252965 /
\ lkml-frank@unternet.org /
-------------------------
[ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est." ]
next prev parent reply other threads:[~2001-11-12 22:58 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 [this message]
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
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=20011112235642.A17544@unternet.org \
--to=lkml-frank@unternet.org \
--cc=jgarzik@mandrakesoft.com \
--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.