{"action":"closed","issue":{"number":41,"created_at":"2011-10-14T21:01:24Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"Many NoSQL databases are able to produce responses in less than a millisecond. When this happens YCSB places the result in the 0 millisecond slot in the histogram array and the latency value not increased (since the latency is reported as zero) and the operations variable is incremented. As a result this causes data for some datastores to be skewed. I suggest using System.nanoTime() and then dividing by 1000 to get the time in microseconds. The histogram will still look the same, but the average latency reported will be much more accurate. Then the documentation could be updated to say that when reading the histogram the value for each slot is between the time of that slot and the next greatest slots time. For example, if there were 1000 operations that were recorded in the 0 slot in the histogram then we would interpret that as \"1000 operation completed in less than 1 millisecond, but greater than 0 milliseconds.\r\n\r\nAlso, for machines that cannot produce time results in the microsecond range we could log a warning that says that that granularity is not supported. I can also submit a patch for this if you are open to the idea.","comments":4,"title":"Sub-Millisecond latencies are reported as taking 0 milliseconds","updated_at":"2011-10-17T20:36:20Z","url":"https://api.github.com/repos/brianfrankcooper/YCSB/issues/41","id":1914120,"assignee":null,"milestone":null,"closed_at":"2011-10-17T20:36:20Z","user":{"gravatar_id":"d3c686cdc7c1d26b83e87cafa462fbba","avatar_url":"https://secure.gravatar.com/avatar/d3c686cdc7c1d26b83e87cafa462fbba?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/mikewied","id":438294,"login":"mikewied"},"html_url":"https://github.com/brianfrankcooper/YCSB/issues/41","labels":[],"state":"closed"},"legacy":{"number":41,"action":"closed","issue":1914120}}