Jeff, averaging is not the correct way to go for latency measuring. We should be using json+ or histogram flow for each bucket IOPS landing. On Wed, Mar 21, 2018 at 11:22 AM, Jeff Furlong <jeff.furlong@xxxxxxx> wrote: > Not sure I understand the question, but you can record max latency per log_avg_msec interval. For example, set log_avg_msec=1000 and then set log_max_value=1 to see the max latency per 1000ms. > > Regards, > Jeff > > > -----Original Message----- > From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of abhishek koundal > Sent: Wednesday, March 21, 2018 10:55 AM > To: fio <fio@xxxxxxxxxxxxxxx> > Subject: Re: FIO latency bin midpoint vs upper limit capture > > Checking back if there is any feedback on the above request for reporting max latency in the bins. > Appreciate the support. > > On Wed, Mar 14, 2018 at 2:07 PM, abhishek koundal <akoundal@xxxxxxxxx> wrote: >> All, >> Currently the FIO latency bins does the i/o count and but then as per >> Lower bound, midpoint (rounded off), upper limit >> >> The reported latency is the based on the "midpoint". >> Is there a way to report it based on the "upper limit"? e.g. compile >> fio with some switch etc. >> >> Appreciate your support always :). >> >> -- >> Life is too short for silly things so invest your time in some >> productive outputs!! > > > > -- > Life is too short for silly things so invest your time in some productive outputs!! > -- > To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- Life is too short for silly things so invest your time in some productive outputs!! -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
