From: Con Kolivas <conman@kolivas.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] Corrected gcc3.2 v gcc2.95.3 contest results
Date: Tue, 24 Sep 2002 00:36:21 +1000 [thread overview]
Message-ID: <1032791781.3d8f26e5c7a05@kolivas.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0209231622100.23588-100000@localhost.localdomain>
Quoting Ingo Molnar <mingo@elte.hu>:
>
> On Mon, 23 Sep 2002, Con Kolivas wrote:
>
> > Agreed. There probably is no statistically significant difference in the
> > different gcc versions.
> >
> > Contest is very new and I appreciate any feedback I can get to make it
> > as worthwhile a benchmark as possible to those who know.
>
> your measurements are really useful i think, and people like Andrew
Thank you. I was beginning to wonder on this.
> started to watch those numbers - this is why at this point a bit more
> effort can/should be taken to filter out fluctuations better. Ie. a single
> fluctuation could send Andrew out on a wild goose chase while perhaps in
> reality his kernel was the fastest. Running every test twice should at
> least give a ballpart figure wrt. fluctuations, without increasing the
> runtime unrealistically.
Absolutely. In my real profession I deal with statistics all the time so I'm
acutely aware of the problem.
> i agree that only the IO benchmarks are problematic from this POV - things
> like the process load and your other CPU-saturating numbers look perfectly
> valid.
Yes, the IO load is proving to be a pain and I'm afraid it will take numerous
measurements to get some idea of the real average. So far the trends in the
results I've reported I think are still correct. The variability, though, that's
another matter.
> obviously another concern to to make testing not take days to accomplish.
> This i think is one of the hardest things - making timely measurements
> which are still meaningful and provide stable results.
I know. Some of the changes I've made to make results reproducible I have
already had complaints about; the situation will only get worse :(
Con
next prev parent reply other threads:[~2002-09-23 14:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 6:55 Con Kolivas
2002-09-23 7:49 ` Ingo Molnar
2002-09-23 10:30 ` Con Kolivas
2002-09-23 11:03 ` jw schultz
2002-09-23 12:47 ` Erik Andersen
2002-09-23 13:00 ` Con Kolivas
2002-09-23 13:15 ` Richard B. Johnson
2002-09-23 13:35 ` Ingo Molnar
2002-09-23 14:09 ` Richard B. Johnson
2002-09-23 18:24 ` Andrew Morton
2002-09-23 14:02 ` Ryan Anderson
2002-09-23 14:15 ` Richard B. Johnson
2002-09-23 14:24 ` Con Kolivas
2002-09-23 14:34 ` Jakub Jelinek
2002-09-23 16:03 ` Måns Rullgård
2002-09-23 14:43 ` Richard B. Johnson
2002-09-24 21:30 ` Bill Davidsen
2002-09-23 16:34 ` Oliver Xymoron
2002-09-23 21:47 ` Con Kolivas
2002-09-24 1:12 ` jw schultz
2002-09-24 9:18 ` Jan Hudec
2002-09-23 14:26 ` Ingo Molnar
2002-09-23 14:36 ` Con Kolivas [this message]
2002-09-24 21:27 ` Bill Davidsen
[not found] <Pine.LNX.4.33.0209232236070.27095-100000@coffee.psychology.mcmaster.ca>
2002-09-24 2:45 ` Con Kolivas
2002-09-24 3:01 ` Andrew Morton
2002-09-24 9:34 ` Jan Hudec
2002-09-24 13:45 ` Denis Vlasenko
2002-09-24 9:26 ` Con Kolivas
2002-09-24 14:19 ` Denis Vlasenko
2002-09-24 15:47 ` Mark Hahn
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=1032791781.3d8f26e5c7a05@kolivas.net \
--to=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®