From: Daniel Phillips <phillips@arcor.de>
To: Nathan Straz <nstraz@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.2 and 2.4 performance issues
Date: Fri, 21 Jun 2002 22:13:09 +0200 [thread overview]
Message-ID: <E17LUmL-0001wL-00@starship> (raw)
In-Reply-To: <20020621171058.GA27100@sgi.com>
On Friday 21 June 2002 19:10, Nathan Straz wrote:
> 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.
There's no sense denying evidence that 2.2 outperforms 2.4 under certain
workloads. Instead we should just be more determined to root out all
those problems and deal with them. There is no inherent design reason
why 2.4 should be slower than 2.2 in any area at all, however, some
practical issues, such as IO scheduling still remain and are being
actively worked on. Expect backports from 2.5 later in the 2.4 series.
For now, the one thing we must not do is risk instability in 2.4, now
that most users have switched over to it.
--
Daniel
next prev parent reply other threads:[~2002-06-21 20:13 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
2002-06-21 20:13 ` Daniel Phillips [this message]
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=E17LUmL-0001wL-00@starship \
--to=phillips@arcor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nstraz@sgi.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