Open Stack

On Mon, Mar 24, 2014 at 9:51 PM, Carl Baldwin <carl at ecbaldwin.net> wrote:

> Don't discard the first number so quickly.
>
> For example, say we use a timeout mechanism for the daemon running
> inside namespaces to avoid using too much memory with a daemon in
> every namespace.  That means we'll pay the startup cost repeatedly but
> in a way that amortizes it down.
>
> Even if it is really a one time cost, then if you collect enough
> samples then the outlier won't have much affect on the mean anyway.
>

It actually affects all numbers but mean (e.g. deviation is gross).


> I'd say keep it in there.
>
> Carl
>
> On Mon, Mar 24, 2014 at 2:04 AM, Miguel Angel Ajo <majopela at redhat.com>
> wrote:
> >
> >
> > It's the first call starting the daemon / loading config files, etc?,
> >
> > May be that first sample should be discarded from the mean for all
> processes
> > (it's an outlier value).
>

I thought about cutting max from counting deviation and/or showing
second-max value. But I don't think it matters much and there's not much
people here who're analyzing deviation. It's pretty clear what happens with
the longest run with this case and I think we can let it be as is. It's
mean value that matters most here.

-- 

Kind regards, Yuriy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140324/18140247/attachment.html>