From: Nathan Straz <nstraz@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.2 and 2.4 performance issues
Date: Fri, 21 Jun 2002 12:10:59 -0500 [thread overview]
Message-ID: <20020621171058.GA27100@sgi.com> (raw)
In-Reply-To: <1024678560.879.27.camel@lpinto>
On Fri, Jun 21, 2002 at 05:55:55PM +0100, Luis Pedro de Moura Ribeiro Pinto wrote:
> I was asked (i'm a company freshman) to perform some tests between
> kernel versions 2.2 and 2.4, and after awhile searching i found a good
> set of benchmarking tools (aim7) from Caldera linux.
Benchmarks are evil. Sure they are useful at times, but for the most
part they get misused. IMHO, aim7 is outdated. The I/O it does it all
very small for today's systems. It's like poking the system with
hundreds of needles. You have no idea how the system will react to a
golf club, baseball bat, sledgehammer or a wet noodle. Sure, some
people really like it and swear by it. Benchmarking is better done with
an application set in mind and best done with the application set
itself.
> Are there better way to perform the test besides using benchmark tools
> like this?
Run the applications you really care about. There is also a good set of
benchmarks, including application specific ones at
http://lbs.sourceforge.net/.
--
Nate Straz nstraz@sgi.com
sgi, inc http://www.sgi.com/
Linux Test Project http://ltp.sf.net/
next prev parent reply other threads:[~2002-06-21 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 16:55 2.2 and 2.4 performance issues Luis Pedro de Moura Ribeiro Pinto
2002-06-21 17:10 ` Nathan Straz [this message]
2002-06-21 20:13 ` Daniel Phillips
2002-06-23 15:37 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2002-06-21 22:58 John L. Males
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=20020621171058.GA27100@sgi.com \
--to=nstraz@sgi.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.