From: Andrew Morton <akpm@digeo.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-mm@kvack.org
Subject: Re: 2.5.42-mm2 on small systems
Date: Mon, 14 Oct 2002 23:42:55 -0700 [thread overview]
Message-ID: <3DABB8EF.5E00AF4E@digeo.com> (raw)
In-Reply-To: <200210140825.29533.tomlins@cam.org>
Ed Tomlinson wrote:
>
> ...
>
> 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.
hm. Works for me. The default setting are waaay too boring, so
I used ./resp -m2 -M5 -w5
Test low high median average median avg
noload 143.168 149.676 143.258 145.602 1.000 1.000
smallwrite 144.319 4350.325 269.161 1428.881 1.879 9.814
largewrite 230.759 1129.816 492.421 539.192 3.437 3.703
cpuload 142.833 207.206 143.374 159.036 1.001 1.092
spawnload 143.066 313.944 143.240 177.391 1.000 1.218
8ctx-mem 159.396 5823.791 810.837 2020.066 5.660 13.874
2ctx-mem 757.203 8192.148 1294.120 2538.975 9.033 17.438
Could be a scheduler thing? Maybe a bug in the test?
--
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-15 6:42 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 ` 2.5.42-mm2 on small systems Ed Tomlinson
2002-10-14 14:34 ` Martin J. Bligh
2002-10-14 21:24 ` Bill Davidsen
2002-10-15 6:42 ` Andrew Morton [this message]
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=3DABB8EF.5E00AF4E@digeo.com \
--to=akpm@digeo.com \
--cc=davidsen@tmr.com \
--cc=linux-mm@kvack.org \
--cc=tomlins@cam.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