From: Con Kolivas <conman@kolivas.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@digeo.com>,
Ryan Anderson <ryan@michonline.com>, Ingo Molnar <mingo@elte.hu>,
"Richard B. Johnson" <root@chaos.analogic.com>,
Oliver Xymoron <oxymoron@waste.org>,
Daniel Jacobowitz <drow@false.org>,
Paolo Ciarrocchi <ciarrocchi@linuxmail.org>,
Robinson Maureira Castillo <rmaureira@alumno.inacap.cl>,
gcc@gcc.gnu.org
Subject: [BENCHMARK] Statistical representation of IO load results with contest
Date: Tue, 24 Sep 2002 09:26:38 +1000 [thread overview]
Message-ID: <1032823598.3d8fa32e92e94@kolivas.net> (raw)
Thank you all who responded with suggestions on how to get useful data out of
the IO load module from contest. These are _new_ results with a
sync,swapoff,swapon before conducting just the IO load. I have digested all your
suggestions and come up with the following:
n=5 for number of samples
Kernel Mean CI(95%)
2.5.38 411 344-477
2.5.39-gcc32 371 224-519
2.5.38-mm2 95 84-105
The mean is a simple average of the results, and the CI(95%) are the 95%
confidence intervals the mean lies between those numbers. These numbers seem to
be the most useful for comparison.
Comparing 2.5.38(gcc2.95.3) with 2.5.38(gcc3.2) there is NO significant
difference (p 0.56)
Comparing 2.5.38 with 2.5.38-mm2 there is a significant diffence (p<0.001)
After playing with all these it appears I should do the following to contest:
Add sync,swapoff,swapon before each load
Perform noload and process_load twice to ensure no abnormal results
Perform mem_load 3 times
Perform IO_fullmem 5 times (and rename it just IO_load)
Drop IO_halfmem (adds no more useful information and just adds time).
Do a statistical analysis like the above when posting information.
Comments?
Con
next reply other threads:[~2002-09-23 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 23:26 Con Kolivas [this message]
2002-09-23 23:41 ` [BENCHMARK] Statistical representation of IO load results with contest Ryan Anderson
2002-09-24 5:28 ` Mike Galbraith
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=1032823598.3d8fa32e92e94@kolivas.net \
--to=conman@kolivas.net \
--cc=akpm@digeo.com \
--cc=ciarrocchi@linuxmail.org \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oxymoron@waste.org \
--cc=rmaureira@alumno.inacap.cl \
--cc=root@chaos.analogic.com \
--cc=ryan@michonline.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 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.