pcp
[Top] [All Lists]

Re: [pcp] pcp updates: pmmgr, pmwebd

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: [pcp] pcp updates: pmmgr, pmwebd
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Tue, 28 Apr 2015 18:58:16 +1000
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20150422000949.GP6822@xxxxxxxxxx>
References: <20150421224405.GN6822@xxxxxxxxxx> <5536E65F.50600@xxxxxxxxxx> <20150422000949.GP6822@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
On 04/22/2015 10:09 AM, Frank Ch. Eigler wrote:
Hi, Mark -

Hey Frank can you post the full git url for your work below.
I'll pull it into a branch for review.

pcpfans.git is git://sourceware.org/git/pcpfans.git
The two subject branches are fche/pmmgr and fche/pmwebd.
Thanks a lot.

- FChE


Howdy Frank, will I just pull in all your changes? Or cherry-pick
only the pmwebd changes? Your tree of unmerged stuff seems to go back
to the commit listed below I think. The pmmgr changes are marked as
'blocked' on https://trello.com/b/5t9Ml341/release-task-tracking.

Cheers
-- Mark


commit 6b2eb46b3eba9dacba86009bfc4ccebd198e7b79
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date:   Sat Feb 28 09:35:09 2015 -0500

    pmwebd: add a "-i MIN-INTERVAL" option for graphite time-precision control

    When pmlogger data is sampled more frequently than /60s, it is
    desirable to let graphite render data at a higher time resolution.
    Oversampling leads to wiggles due to interpolation FP artifacts, so is
    undesirable.  The pmwebd invoker is best placed to judge the right
    tradeoff, so is given an option to set the minimum time-step size.











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