All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@ufl.edu>
To: Stan Bubrouski <stan@ccs.neu.edu>
Cc: Con Kolivas <conman@kolivas.net>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.51 with contest
Date: 10 Dec 2002 16:05:27 -0500	[thread overview]
Message-ID: <1039554327.846.1128.camel@phantasy> (raw)
In-Reply-To: <3DF64852.9030006@ccs.neu.edu>

On Tue, 2002-12-10 at 15:02, Stan Bubrouski wrote:

> I disagree, 2.4.20 is the current stable kernel, it would
> be nice to see how it compares to the current development,
> what's faster, what's not... from Con's previous results
> we can see that some things are indeed not as fast in 2.5.x
> as in 2.4.x.  It's just nice to be able to see the whole
> picture.  I often follow these threads for just this purpose.

Like I said, that may give users warm fuzzies or be helpful to marketing
folks but Con's benchmark is not really useful for _helping developers_
wrt comparing 2.4 vs 2.5.

A benchmark like AIM9, which is a bunch of micro-benchmarks, is useful
because we can say "look truncating a zero-length file is a lot slower
now".

But a contest result from 2.4 to 2.5 tells us what?  Especially since
lower times in contest may not even be bad.  Contest is invaluable for
testing one change vs. without.  In fact, I would venture to say Con's
work is a big reason why 2.5 has the fairness and interactive
performance it does.  But it is not so helpful to see changes since 2.4.

	Robert Love


  parent reply	other threads:[~2002-12-10 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 11:44 [BENCHMARK] 2.5.51 with contest Con Kolivas
2002-12-10 17:18 ` Stan Bubrouski
2002-12-10 18:45   ` Robert Love
2002-12-10 20:02     ` Stan Bubrouski
2002-12-10 20:51       ` Arador
2002-12-10 21:05       ` Robert Love [this message]
2002-12-10 20:24   ` Con Kolivas

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=1039554327.846.1128.camel@phantasy \
    --to=rml@ufl.edu \
    --cc=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stan@ccs.neu.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 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.