Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2533
I ran FastWordCount with 1.1.1, and it is showing similar latency even from
1.1.1. Complete latency is calculated from acker receiving ACKER_INIT to acker
completing tuple tree, hence it contains all the latency: tuple waiting a
queue, transferring, etc, and so if the topology is heavily overloaded it can
be a bit off.---
