Not quite... if we don't `Reset` and the stream has been running for a long time, then any recent problems with message handling won't show up -- the percentile values will be overwhelmed by the vast amount of data we had in the past.

We need to reset somehow, the question is how often.  The "correct" thing to do would be to roll a couple of these suckers together so we have a smooth moving window.  Since that would increase the overhead, I think having the Resets to zero and also returning out values of what data the quantile uses would be sufficient.

Also, for synchronization, I think the main point is to synchronize the statsd calls since there you want to have a more holistic view.  This could be done easily by moving the statsd calls to add this data be separate and be called right before a reset.