Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
STORM-2912 Revert optimization of sharing tick tuple #2533
Ran the FastWordCount with and without this patch, the number dont look much different. FastWordcount is expected not to see any difference ? Maybe we can wait for Alexandre's results.
Storm 1.2.0 RC1
With the patch
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.