From: jw schultz <jw@pegasys.ws>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.74-mm1 with contest
Date: Thu, 3 Jul 2003 18:08:08 -0700 [thread overview]
Message-ID: <20030704010808.GB9719@pegasys.ws> (raw)
In-Reply-To: <200307040132.55827.kernel@kolivas.org>
On Fri, Jul 04, 2003 at 01:32:55AM +1000, Con Kolivas wrote:
> Here are contest benchmarks for 2.5.74-mm1 with my scheduler tweaks:
>
[snip]
>
> A little more here, a little less there. No major changes except for dbench
> load which appears to have significantly shorter compile times. As kernel
> compiles are not by their nature "interactive", these results are expected.
> It is nice to see that it doesn't appear to starve any load unecessarily as
> well.
>
> Contest can show the kernel's ability to perform in the setting of different
> loads without being choked, but will not show if your audio application will
> get to play when it wants to, nor whether your windows will move around the
> screen smoothly.
>
> Con
>
> P.S. Does anyone see the irony in the fact that my own benchmark won't show
> that my patch does anything?
I see no irony, and much value, in your benchmark showing
that your patch doesn't break server performance.
Perhaps a load that generated X events to move a window
around in an ellipse or polygon would show some effects of
your patch.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
prev parent reply other threads:[~2003-07-04 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 15:32 [BENCHMARK] 2.5.74-mm1 with contest Con Kolivas
2003-07-04 1:08 ` jw schultz [this message]
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=20030704010808.GB9719@pegasys.ws \
--to=jw@pegasys.ws \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox