Those tools all make use of a pool of workers. Say you want 1000 RPS, they&#x27;ll make something like 100 workers and make them do 10 RPS each.  To make 10 RPS each, their requests all must take at most 100ms each. The issue of coordinated omission arises when those requests take more than 100ms each and the rate of requests your measuring becomes distorted. This is well explained if you read Gil Tene:<p><a href="https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!msg&#x2F;mechanical-sympathy&#x2F;icNZJejUHfE&#x2F;BfDekfBEs_sJ" rel="nofollow">https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!msg&#x2F;mechanical-sympathy&#x2F;ic...</a><p>How to avoid this error yourself?  Don&#x27;t make a pool of workers, have each 1000 requests be their own thread&#x2F;goroutine. So you&#x27;ll create 1000 goroutines per second, each of them doing their own request. This way you won&#x27;t omit measurements by skipping beats.