On Mon, Jan 4, 2016 at 9:29 AM, Ben Ripkens <[email protected]> wrote: >> I don't think there is a need to build in "lag" calculation, libuv > users can track that themselves by combining a uv_prepare_t and > uv_check_t handle. > > Sorry, I didn't mean to propose it as an addition to libuv. I am interested > in whether or not you would say that this metric makes sense. A lot of > factors can influence this "lag" and I find it hard to decide which values > are good or bad.
FWIW, in StrongLoop's strong-agent product, we measure the avg/min/max/stddev over a period of time without trying to interpret the numbers, we just plot it. If you want to discriminate between "good" and "bad" samples, you have to put in fairly arbitrary thresholds. -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
