From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel M/L <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Con Kolivas <kernel@kolivas.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Scheduler smoothness and fairness - results and package
Date: Tue, 22 May 2007 10:27:59 -0400 [thread overview]
Message-ID: <4652FDEF.8060209@tmr.com> (raw)
Thanks to the suggestions of several people and some encouragement, I've
done another upgrade of the schedular characteristic package glitch1.
For "bottom line" folks, the results are at
http://www.tmr.com/~davidsen/sched_smooth_03.html
This package runs four fast scrolling xterms and a copy of glxgears to
produce both screen update and CPU load. In addition to the human
observation of smoothness, the glxgears speeds are characterized by
variance from sample to sample, and the number of random numbers
generated by the xterm programs are also characterized.
Changes:
- Reruns for a given configuration are shown in a single row.
- The analysis has had minor output format and statistical tweaks for
correctness as well as handling of multiple run output in a single row.
- the glxgears 1st value is shown as a separate item, since there is a
large stoppage on the first sample after cold boot with some schedulers.
The full source and doc is now available from
http://www.tmr.com/~public/source/
so people can do their own runs. Note that values between different
machines are almost certainly not meaningful.
Having run all this on a dual core Core2duo in x86 (32 bit) mode, I'm
now off to rerun in x86_64 mode, and on a single CPU hyperthreaded
machine, and a pure uniprocessor. I'm going to create a page for all the
results in one place for anyone who cares.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
reply other threads:[~2007-05-22 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4652FDEF.8060209@tmr.com \
--to=davidsen@tmr.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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 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.