https://bugzilla.redhat.com/show_bug.cgi?id=1296750
--- Comment #7 from Frank Ch. Eigler <fche@xxxxxxxxxx> ---
> This reading of PM_MODE_INTERP doesn't seem incompatible with pmSetMode's
> documentation, or the programming guide.
Thinking about it more, it's even more appropriate in a way. The whole
idea of INTERP mode is that the client doesn't want to know the ebb and
flow of the actual underlying data: it wants to pretend as if only its
pmFetch() timing mattered. So one could argue that interp.c would be
more correct to analyze by pmFetch time intervals rather than archive
records' time intervals.
(This could go beyond the <mark> analysis we're talking about now; it
could relate to taking interpolation/averaging over multiple samples
in the given time window, not just the immediately-adjacent ones.)
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=NhFrWRhAFS&a=cc_unsubscribe
|