Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Statistics getTotalGetLatency, getTotalRemoveLatency, getTotalPutLatency works incorrectly #10938
Local statistics uses milliseconds for get/put/remove latencies. It is very usual for latencies to be around microseconds, hence the values may become 0 very easily. Especially the accumulative statistics such as totalGetLatencies and such, it does not make sense to stay at 0 even though there are millions of gets each below millisecond latency.
E.g. Our get latency for a single get is usually in microseconds around 100-200usecs. If you do 1 million get, then we normally expect the latency to be 1 million * 200 usec=200 sec. But since latency for each request is less than a millisecond, it is recorded as to be zero and the total becomes zero.