mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Morton <chromi@cyberspace.org>
To: Rik van Riel <riel@conectiva.com.br>, nbecker@fred.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: regression testing
Date: Thu, 22 Mar 2001 18:12:47 +0000	[thread overview]
Message-ID: <l03130302b6dfea87c17f@[192.168.239.101]> (raw)
In-Reply-To: <Pine.LNX.4.21.0103221334570.21415-100000@imladris.rielhome.conectiva>
In-Reply-To: <x88zoeeeyh8.fsf@adglinux1.hns.com>

>- automated heavy stress testing

This would be an interesting one to me, from a benchmarking POV.  I'd like
to know what my hardware can really do, for one thing - it's all very well
saying this box can do X Whetstones and has a 100Mbit NIC, but it's a much
more solid thing to be able to say "my box handled the official Foobar
stress-test in Y hours, handling Z widgets per second".

The lmbench statistics are nice, but most of those numbers mean absolutely
nothing to all but übergeeks (what they say to my partially-trained ears is
that my gateway box sucks, but then again it's five-year-old Intel hardware
so that could probably have been predicted).  Are there already
stress-testing kits for user-level processes I could play with?

What would be *really* interesting would be to make such tests as portable
as practical, so that at least some of them can be run on "rival platforms"
(such as *cough* Redmondware) to see if they stand up to the challenge as
well.

However, if the focus is on *kernel* stress-testing, portability might be a
little difficult to arrange for many tests.  The basics could probably be
written portably or ported easily, though - things that lmbench already
(briefly) benchmarks, for example.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----



  parent reply	other threads:[~2001-03-22 18:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 13:15 nbecker
2001-03-22 13:39 ` Richard B. Johnson
2001-03-22 13:47   ` nbecker
2001-03-22 14:47   ` Alan Cox
2001-03-22 14:45     ` Richard B. Johnson
2001-03-22 18:18   ` Cort Dougan
2001-03-22 15:13 ` Wade Hampton
2001-03-22 15:56   ` Nathan Straz
2001-03-22 16:46     ` Nathan Dabney
2001-03-22 16:37 ` Rik van Riel
2001-03-22 18:21   ` Cort Dougan
2001-03-22 18:12 ` Jonathan Morton [this message]
2001-03-23 15:00   ` Horst von Brand
2001-03-23 15:29     ` Rik van Riel
2001-03-23 10:11 ` Eric W. Biederman
2001-03-27  7:21   ` Werner Almesberger
2001-03-22 18:44 Torrey Hoffman

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='l03130302b6dfea87c17f@[192.168.239.101]' \
    --to=chromi@cyberspace.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbecker@fred.net \
    --cc=riel@conectiva.com.br \
    /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®