On Tuesday, 11 October 2016 at 13:22:48 UTC, Dicebot wrote:
On 10/11/2016 04:13 PM, Joakim wrote:
On Monday, 10 October 2016 at 08:47:54 UTC, Robert burner Schadek wrote:

Never heard about this either, I ignore node.js stuff. I was just reading this interesting post on tracing/profiling a couple days ago: is it efficient enough to find some of these tail latency issues?

Stats aggregation usually has nothing to do with fine tuned performance profiling - it is application defined way to monitor relevant metrics of runtime behavior. For example, one can aggregate metrics for web app request processing latencies to monitor if those stay within expected margin - but if issue is spotted, it won't help much in debugging _why_ it has happened.

Sure, it's not meant for tracing but monitoring, but if it is efficient enough you could repurpose it to specifically instrument for certain slow paths you're seeing. The question is: how efficient is it?

Reply via email to