It should be a windowed average measure of the time between when the component receives a tuple and when it acks the tuple.
This can be slower if there is batching, aggregating, or joining happening (the component must wait for a number of other tuples to arrive before it can ack). On the UI, there are tool tips that explain the measurements. They appear after hovering over the label. -- Derek On 7/9/14, 15:22, Raphael Hsieh wrote:
Can somebody explain to me what might cause the spout to have a large process latency? Currently my spout0 and $spoutcoord-spout0 have latency's higher than I would like. I'm consuming data from a Kafka stream. How is this process latency measured ? Is it measuring the amount of time it takes to fill a batch with data and send it to the first bolt in the topology? Thanks
