Thanks. It looks promising.
Denis
Le 24/09/2015 14:30, Onur Yalazı a écrit :
I am using nonblocking statsd client and statsd and graphite for a
relatively similar purpose.
Statsd uses udp for collecting metrics and graphite is too good with
working on these metrics. You can calculate min/max/avg duration of
your topology with this way.
On Sep 24, 2015 3:23 PM, "Denis DEBARBIEUX" <[email protected]
<mailto:[email protected]>> wrote:
Hi all,
I would like to compute the latency of my topology (time spend by
a message form the spout to the end of my topology).
Until now, I enable the acking (1 acker per worker) and I get the
result in storm UI. But today I discover that disable the acking
seep up my topology by a factor of 10 (unit: tupes per second).
I also try to compute this value by my self by seting a time stamp
in the tuples in the spout. Then I compute the lantency at the end
of the topology. As the clocks of my machies are not synchronized,
I get very strange results.
So my question is how to compute the latency with a weak
algorithm/tool.
Thanks for your help.
Regads,
D. Debarbieux
------------------------------------------------------------------------
Avast logo <https://www.avast.com/antivirus>
L'absence de virus dans ce courrier électronique a été vérifiée
par le logiciel antivirus Avast.
www.avast.com <https://www.avast.com/antivirus>
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
https://www.avast.com/antivirus
