From: Dan Kegel <dank@alumni.caltech.edu>
To: linux-kernel@vger.rutgers.edu
Subject: Regression testing?
Date: Wed, 20 Jan 1999 08:41:54 -0800 [thread overview]
Message-ID: <36A60752.668C9631@alumni.caltech.edu> (raw)
In-Reply-To: 19990120031127Z157444-8100+9173@vger.rutgers.edu
Does anyone have access to some hefty benchmarks
suites like SPEC's, or regression tests
like the POSIX compliance test?
It might be a good idea to run 2.2.0-pre-x
through these to look for suprises
before going final with it.
The Posix test suite is downloadable from
http://www.itl.nist.gov/div897/ctg/posix_form.htm
See also http://www.standards.ieee.org/regauth/posix/
Even if we didn't actually pass all the tests,
it'd be good to know that we didn't oops.
The SPEC benchmarks can be purchased at
http://www.spec.org/cgi-bin/osgorder
for $700 or so. The hard part is
actually having the patience to run them.
(I suspect if Linux or Alan asked nicely, they'd
donate a benchmark or two. Or we could take
up a collection. Or Alan's boss could pay.)
Three of the SPEC tests look interesting:
SPECweb96 stresses out HTTP networking.
SPEC SFS97 stresses out NFS networking.
SPEC SDM (System Development: Multitasking)
stresses the kernel by simulating a large number of
users running make, cp, diff, etc.
The point of running these benchmarks is not really
to say we're fast, but to see whether we can
actually get all the way through the benchmark
(which might take a day to run) without having
a functional error or a crash.
- Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
parent reply other threads:[~1999-01-21 2:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <19990120031127Z157444-8100+9173@vger.rutgers.edu>]
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=36A60752.668C9631@alumni.caltech.edu \
--to=dank@alumni.caltech.edu \
--cc=linux-kernel@vger.rutgers.edu \
/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