From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Isaac To <isaac.to@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Error report: perfbook Section 11.6.3.2
Date: Sat, 26 Jul 2014 09:51:33 -0700 [thread overview]
Message-ID: <20140726165133.GM11241@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOArY3UOo6mk=y5yQi+mqvRfrduJodYOE0tL3ioyAx4qx-Lfww@mail.gmail.com>
On Sat, Jul 26, 2014 at 04:47:51PM +0800, Isaac To wrote:
> On Tue, Jul 22, 2014 at 11:57 PM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> >> The probability being calculated needs to be specified like "the
> >> probability of this happening *in case* the fix has no effect". That "the
> >> fix has no effect" needs to be a *prerequisite*, and cannot itself be the
> >> probability to be computed. The complement, i.e., 1 - 1.2e-8, is "the
> >> confidence level that the probability of failing is less than the
> >> original". I'd suggest using the "confidence level" wording here, but
> >> explain what it is earlier in the book to tell the less mathematically apt
> >> readers understand the wordings.
> >
> > Good catch!
> >
> > How about if I reworded that paragraph as follows?
> >
> > Suppose that a given test fails about once every hour, but after a
> > bug fix, a 24-hour test run fails only twice. Assuming that the
> > failure leading to the bug is a random occurrence, and further
> > assuming that the alleged fix actually had no effect on this
> > particular bug, what is the probability that the small number
> > of failures in the second run was due to random chance? This
> > probability may be calculated by summing Equation 11.26 as
> > follows:
>
> I think if you already say "assuming that the failure ... is a random
> occurrence", then "was due to random chance" is redundant. Perhaps
> "What is the probability of the small number of failures, assuming
> that the alleged fix actually has no effect on the test failure?"
> suffices. On the other hand, that would not be very consistent with
> other parts of the book that uses the "confidence level" terminology.
> And the term is not defined elsewhere either.
OK, I now say the following, which removes the redundancy but links to
the concept of confidence:
Suppose that a given test fails about once every hour, but after
a bug fix, a 24-hour test run fails only twice. Assuming that
the failure leading to the bug is a random occurrence, what
is the probability that the small number of failures in the
second run was due to random chance? In other words, how
confident should we be that the fix actually had some effect
on the bug? This probability may be calculated by summing
Equation 11.26 as follows:
> > I am shying away from explaining "confidence level" because I haven't
> > yet come up with a compact and accurate way of doing so. However, I am
> > taking this email as encouragement to keep trying. ;-)
>
> Yes that is hard. Actually I like the confidence level wording more,
> not only because it is more compact, but also because the wording
> clearly explain why the probability calculated is noteworthy. On the
> other hand, I think the book is more on programming rather than
> mathematics, so I won't complain if the book does not try to teach
> fancy statistical ideas if that is not needed in the main theme.
Well, I do say this earlier on:
These tools are extremely helpful, but please note that reading
this section not a substitute for taking a good set of statistics
classes.
And in case you were wondering about the derivation of the Poisson CDF,
that will be moving to an appendix shortly, and will probably be dropped
entirely to make room for more relevant things. What can I say? I was
too proud of suddenly realizing how to derive it from scratch. ;-)
Thanx, Paul
prev parent reply other threads:[~2014-07-26 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 8:24 Error report: perfbook Section 11.6.3.2 Isaac To
2014-07-22 15:57 ` Paul E. McKenney
2014-07-26 8:47 ` Isaac To
2014-07-26 16:51 ` Paul E. McKenney [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=20140726165133.GM11241@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=isaac.to@gmail.com \
--cc=perfbook@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 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.