From: Ed Tomlinson <tomlins@cam.org>
To: Andrew Morton <akpm@digeo.com>, Bill Davidsen <davidsen@tmr.com>
Cc: linux-mm@kvack.org
Subject: 2.5.42-mm2 on small systems
Date: Mon, 14 Oct 2002 08:25:29 -0400 [thread overview]
Message-ID: <200210140825.29533.tomlins@cam.org> (raw)
In-Reply-To: <3DA9FA51.2E4129E8@digeo.com>
Hi,
I have an old 486 with 64m and 512M of disk that I use as a serial console.
It does not have enough space to be useful for much else. So I decided to
test the low end and tried it with 2.5.42-mm2. It boots and seems to work
fine. Then I tried the resp1 (http://pages.prodigy.net/davidsen/) benchmark.
With 2.4.18 it works:
Memory size 61 MB
Starting 1 CPU run with 61 MB RAM, minimum 5 data points at 20 sec intervals
. . . . . . . .
_____________ delay ms. ____________
Test low high median average S.D. ratio
noload 2128.527 2138.035 2129.915 2131.269 0.003 1.000
smallwrite 4178.129 27436.634 4318.342 11111.745 8.927 5.214
largewrite 4157.574 78592.200 4222.064 16336.681 24.926 7.665
cpuload 6109.576 8018.156 6230.810 6425.307 0.600 3.015
spawnload 5508.218 6934.219 5556.992 5706.077 0.462 2.677
8ctx-mem 10090.974 22222.700 12662.532 13511.634 3.433 6.340
2ctx-mem 9330.010 21106.194 10745.474 11650.974 3.612 5.467
with 2.5.42-mm2 it does not finish. The machine is sort of usable while its runing
and control C has no problem ending the program. I waited 11 hours for the spawnload
test to complete - it was looking very good before this....
Memory size 61 MB
Starting 1 CPU run with 61 MB RAM, minimum 5 data points at 20 sec intervals
. . . . . . . .
_____________ delay ms. ____________
Test low high median average S.D. ratio
noload 2262.747 2269.895 2264.050 2264.796 0.002 1.000
smallwrite 3797.901 12132.336 3875.934 5364.276 2.815 2.369
largewrite 3857.445 35682.893 3875.064 8405.061 10.531 3.711
cpuload 5385.148 7589.479 5514.157 5771.985 0.729 2.549
The box was not limited by IO (no swapping nor was there much bi/bo in
vmstat). About 25% User and 75% system in cpu though.
Ed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-14 12:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 16:04 2.5.42-mm2 hangs system Henrik Størner
2002-10-13 21:03 ` William Lee Irwin III
[not found] ` <3DA9CA28.155BA5CB@digeo.com>
2002-10-13 22:33 ` Henrik Størner
2002-10-13 22:57 ` Andrew Morton
2002-10-14 12:25 ` Ed Tomlinson [this message]
2002-10-14 14:34 ` 2.5.42-mm2 on small systems Martin J. Bligh
2002-10-14 21:24 ` Bill Davidsen
2002-10-15 6:42 ` Andrew Morton
2002-10-16 20:55 ` Bill Davidsen
2002-10-16 22:43 ` Ed Tomlinson
2002-10-16 13:09 ` 2.5.42-mm2 hangs system Maneesh Soni
2002-10-16 15:49 ` Henrik Størner
2002-10-16 18:59 ` Henrik Størner
2002-10-16 19:31 ` Dipankar Sarma
2002-10-16 19:43 ` Andrew Morton
2002-10-16 20:05 ` Dipankar Sarma
2002-10-30 9:48 ` [FIX] " Maneesh Soni
2002-10-31 7:54 ` Henrik Størner
2002-10-17 14:38 ` Maneesh Soni
2002-10-17 16:14 ` 2.5.43-mm2 gets network connection stuck Sebastian Benoit
2002-10-17 17:22 ` Andrew Morton
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=200210140825.29533.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=akpm@digeo.com \
--cc=davidsen@tmr.com \
--cc=linux-mm@kvack.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