From: Mikael Pettersson <mikpe@csd.uu.se>
To: axboe@suse.de, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.2-pre performance degradation on an old 486
Date: Sat, 5 Jan 2002 01:51:41 +0100 (MET) [thread overview]
Message-ID: <200201050051.BAA16036@harpo.it.uu.se> (raw)
When running 2.5.2-pre7 on my old for-testing-only 486(*),
file-system accesses seem to come in distinct bursts preceded
by lengthy pauses. Overall performance is down quite significantly
compared to 2.4.18pre1 and 2.2.20pre2. To measure it I ran two
simple tests:
Test 1: time to boot the kernel, from hitting enter at the LILO
prompt to getting a login prompt
Test 2: time to "rm -rf" a clean linux-2.4.17 source tree, using
the newly booted kernel (no other access to the tree before that,
so it wasn't cached in any way, and the machine was otherwise idle)
Test 1 Test 2
2.2.21pre2: 71 sec 75 sec
2.4.18pre1: 64 sec 72 sec
2.5.2-pre7: 97 sec 251 sec
I haven't noticed any slowdowns on my other boxes, so I didn't
do any measurements on them. On the 486 it's very very obvious.
/Mikael
(*) 100MHz 486DX4, 28MB ram, no L2 cache, two old and slow IDE disks,
small custom no-nonsense RedHat 7.2, kernels compiled with gcc 2.95.3.
next reply other threads:[~2002-01-05 0:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 0:51 Mikael Pettersson [this message]
2002-01-05 8:25 ` Matthias Hanisch
2002-01-05 23:10 ` Davide Libenzi
2002-01-06 10:21 ` Jens Axboe
2002-01-06 10:33 ` Andre Hedrick
2002-01-06 23:59 ` [patch] 2.5.2 scheduler code for 2.4.18-pre1 ( was 2.5.2-pre performance degradation on an old 486 ) Davide Libenzi
2002-01-07 1:38 ` Andrea Arcangeli
2002-01-07 14:35 ` J.A. Magallon
2002-01-07 14:37 ` Andrea Arcangeli
2002-01-07 7:32 ` Jens Axboe
2002-01-07 18:10 ` Davide Libenzi
2002-01-07 7:22 ` 2.5.2-pre performance degradation on an old 486 Matthias Hanisch
2002-01-07 16:43 ` Linus Torvalds
2002-01-07 18:31 ` Davide Libenzi
2002-01-07 21:43 ` Matthias Hanisch
2002-01-07 22:17 ` Davide Libenzi
2002-01-07 18:01 Mikael Pettersson
2002-01-07 18:36 ` Davide Libenzi
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=200201050051.BAA16036@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®