On Mon, Oct 15, 2018 at 12:09 PM Vincent Fu <vincentfu@xxxxxxxxx> wrote:
>
> On 10/11/2018 01:51 PM, smitha sunder wrote:
> >>From the JSON output :
> > "latency_us" : {
> > "2" : 11.500203, <----
> > "4" : 40.336987,
> > "10" : 2.821762,
> > "20" : 0.121803,
> > "50" : 0.020300,
> > "100" : 0.000000,
> > "250" : 0.000000,
> > "500" : 0.000000,
> > "750" : 0.000000,
> > "1000" : 0.000000
> > },
> >
> > Terse output :
> > lat_2us 56.70% <---
> > lat_4us 40.34%
> > lat_10us 2.82%
> > lat_20us 0.12%
> > lat_50us 0.02%
> > lat_100us 0.00%
> > lat_250us 0.00%
> > lat_500us 0.00%
> > lat_750us 0.00%
> > lat_1000us 0.00%
>
> This is because the terse output has no nanosecond latency values. So
> the terse lat_2us bucket includes everything below 2us.
>
> The JSON latency_us 2 bucket includes only the percentage from 1-2us.
> There should also be a "latency_ns" JSON object with the percentage
> distribution for latencies under 1us. If you add up all those along with
> the latency_us 2 value of 11.5, you should get 56.7%.
Thanks Vicent! Appreciate the help!
Here it is :
"latency_ns" : {
"2" : 0.000000,
"4" : 0.000000,
"10" : 0.000000,
"20" : 0.000000,
"50" : 0.000000,
"100" : 0.030451,
"250" : 1.421031,
"500" : 4.496549,
"750" : 3.664231,
"1000" : 35.586683
},
"latency_us" : {
"2" : 11.500203,
"4" : 40.336987,
"10" : 2.821762,
"20" : 0.121803,
"50" : 0.020300,
"100" : 0.000000,
"250" : 0.000000,
"500" : 0.000000,
"750" : 0.000000,
"1000" : 0.000000
},
"latency_ms" : {
"2" : 0.000000,
"4" : 0.000000,
"10" : 0.000000,
"20" : 0.000000,
"50" : 0.000000,
"100" : 0.000000,
"250" : 0.000000,
"500" : 0.000000,
"750" : 0.000000,
"1000" : 0.000000,
"2000" : 0.000000,
">=2000" : 0.000000
},
Thanks
smitha
