From: Matt Keenan <tank.en.mate@gmail.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Ray Lee <ray@madrabbit.org>,
Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: Sched - graphic smoothness under load - cfs-v13 sd-0.48
Date: Mon, 21 May 2007 19:27:52 +0100 [thread overview]
Message-ID: <4651E4A8.7010009@gmail.com> (raw)
In-Reply-To: <464F99EC.3080006@tmr.com>
Bill Davidsen wrote:
> Ray Lee wrote:
>> On 5/19/07, Bill Davidsen <davidsen@tmr.com> wrote:
>>> I generated a table of results from the latest glitch1 script, using an
>>> HTML postprocessor I not *quite* ready to foist on the word. In any
>>> case
>>> it has some numbers for frames per second, fairness of the processor
>>> time allocated to the compute bound processes which generate a lot of
>>> other screen activity for X, and my subjective comments on how
>>> smooth it
>>> looked and felt.
>>>
>>> The chart is at http://www.tmr.com/~davidsen/sched_smooth_01.html for
>>> your viewing pleasure.
>>
>> Is the S.D. columns (immediately after the average) standard
>> deviation? If so, you may want to rename those 'stdev', as it's a
>> little confusing to have S.D. stand for that and Staircase Deadline.
>> Further, which standard deviation is it? (The standard deviation of
>> the values (stdev), or the standard deviation of the mean (sdom)?)
>>
> What's intended is the stddev from the average, and perl bit me on
> that one. If you spell a variable wrong the same way more than once it
> doesn't flag it as a possible spelling error.
>
> Note on the math, even when coded as intended, the divide of the
> squares of the errors is by N-1 not N. I found it both ways in online
> doc, but I learned it decades ago as "N-1" so I used that.
N-1 is for estimating the standard deviation from a random sample of a
population (s), N is for calculating the standard deviation of a whole
population (σ).
xref http://en.wikipedia.org/wiki/Standard_deviation
Yes, I am aware of the potential for Wikipedia articles to be wrong, but
this article seems correct at first blush :)
Matt
next prev parent reply other threads:[~2007-05-21 18:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 20:02 Sched - graphic smoothness under load - cfs-v13 sd-0.48 Bill Davidsen
2007-05-19 20:22 ` Ray Lee
2007-05-20 0:44 ` Bill Davidsen
2007-05-20 6:12 ` Michael Gerdau
2007-05-20 6:30 ` Ray Lee
2007-05-20 6:59 ` Michael Gerdau
2007-05-20 7:20 ` Ray Lee
2007-05-20 6:55 ` Ray Lee
2007-05-21 18:27 ` Matt Keenan [this message]
2007-05-19 20:36 ` Diego Calleja
2007-05-19 20:55 ` Ray Lee
2007-05-19 23:21 ` Mike Galbraith
2007-05-20 16:29 ` Miguel Figueiredo
2007-05-20 16:44 ` Ray Lee
2007-05-20 16:58 ` Miguel Figueiredo
2007-05-20 17:19 ` Ray Lee
2007-05-22 17:55 ` Bill Davidsen
2007-05-22 20:01 ` Miguel Figueiredo
2007-05-23 0:28 ` Bill Davidsen
2007-05-23 13:10 ` Bill Davidsen
2007-05-23 18:29 ` Miguel Figueiredo
2007-05-23 20:45 ` Bill Davidsen
2007-05-23 21:03 ` Miguel Figueiredo
2007-05-24 0:36 ` Con Kolivas
2007-05-23 4:06 ` William Lee Irwin III
2007-05-23 5:23 ` Michael Gerdau
2007-05-23 7:58 ` Xavier Bestel
2007-05-23 8:21 ` Bill Huey
2007-05-23 18:22 ` Ian Romanick
2007-05-23 18:43 ` Xavier Bestel
2007-05-23 17:22 ` Bill Davidsen
2007-05-23 16:59 ` Bill Davidsen
2007-05-22 17:22 ` Bill Davidsen
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=4651E4A8.7010009@gmail.com \
--to=tank.en.mate@gmail.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray@madrabbit.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