pcp
[Top] [All Lists]

Re: [pcp] Floating point problem

To: Martin Spier <mspier@xxxxxxxxxxx>
Subject: Re: [pcp] Floating point problem
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 31 Jul 2014 10:33:51 +1000
Cc: Brendan Gregg <bgregg@xxxxxxxxxxx>, pcp@xxxxxxxxxxx, Amer Ather <aather@xxxxxxxxxxx>, Coburn Watson <cwatson@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <CAEp4+dWXWKHWOHD0HACaRnXge7tu8QFGu_R2283EOatLsngXhQ@xxxxxxxxxxxxxx>
References: <CAEp4+dU2kE9JJztBPc=N5oSyoEyBvN5Of19rohC3DxXGeomuRw@xxxxxxxxxxxxxx> <033501cfa8a4$fd091ed0$f71b5c70$@internode.on.net> <CAEp4+dUH6fEQ2E=o5O2q8LKfR2xUypM-AeOwQhWy9sEntvO-AQ@xxxxxxxxxxxxxx> <53D6CE6A.8030309@xxxxxxxxxxxxxxxx> <CAJN39oi=_+NkcsKGcuVdiqT=m8cqoB0wF6v1xakSOPQmYdV4-g@xxxxxxxxxxxxxx> <53D978ED.8010100@xxxxxxxxxxxxxxxx> <CAEp4+dWXWKHWOHD0HACaRnXge7tu8QFGu_R2283EOatLsngXhQ@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
On 31/07/14 09:51, Martin Spier wrote:
My understanding was that the original metrics, kernel.all.cpu.user and
kernel.all.cpu.sys suffered from the same problem. If that's not the
case, I completely agree with option 2.

I do not believe the underlying metrics have any related semantic issues ... they preserve full precision (as much as you can packing a struct timeval in units of sec + usec into an unsigned 64-bit integer in units of msec), up to integer overflow (which can even be handled algorithmically in the client if you want to add extra credit points).

<Prev in Thread] Current Thread [Next in Thread>