From: Arjan van de Ven <arjanv@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Preliminary testing results for 2.4.10-pre11
Date: Tue, 18 Sep 2001 15:51:21 -0400 [thread overview]
Message-ID: <20010918155121.B26279@devserv.devel.redhat.com> (raw)
Hi.
In the Red Hat testlab, Bob Matthews has run the stress-test part of our
normal "release signoff tests" on 2.4.10pre11 to evaluate the new VM for
stability.
So far, tests were done on 2 different machines, both using a kernel
compiled with PAE support (HIGHMEM64G).
"Test4" is a 4xPIII machine with 2Gb RAM and 4Gb swap
"Test30" is a 2xPIII machine with 1GB RAM and 2Gb swap
Neither of these machines passed the test; 2.4.7-ac3 (as used in Red Hat
beta Roswell 2) and 2.4.9-ac kernels do pass these tests.
Test4: Random failures of memtst, apparently due to OOM. Random failure of
file system tests, cause unknown.
Test30: Random failures of memtst, TTCP, the file system tests and the
floating point tests, all apparently due to OOM. OOM killed test harness,
can not continue.
("OOM" is "OOM killing process X" and "VM: killing process X")
Similar behavior has been obseverved with the 2.4.6-ac5 kernel, which at the
time turned out to have the bug that the VM subsystem never waited for ANY
io to complete, which meant the kernel couldn't satisfy new allocations
while there were actually plenty of dirty pages around.
About the test
--------------
The test can be downloaded from http://people.redhat.com/bmatthews/cerberus
and consists of a superset of the Cerberus testsuite as published by VA
Linux, and is used by Red Hat and other distributions to test the stability
of kernels for distribution releases.
The tests scale to memory, but make sure that at least 500Mb (for small
machines) or 1Gb (for bigger machines) swapspace is "slack" eg, on a 2GB Ram
/ 4Gb swap machine, no more than 5Gb is used for the workload. The test is
by no means a speed-indication, only a stability test.
Greetings,
Arjan van de Ven
reply other threads:[~2001-09-18 19:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010918155121.B26279@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--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