That is how the tool does by default unless it has been changed in the 3.0+ versions where there are no bins but completion time vs iops landing in that zone. If I recall prior to 3.0, it was bins -> 0 , 1 ...12xx. On Wed, Mar 21, 2018 at 10:59 AM, Kris Davis <Kris.Davis@xxxxxxx> wrote: > What are you doing to see a "report" of the mid latency? > > Kris Davis > > -----Original Message----- > From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of abhishek koundal > Sent: Wednesday, March 21, 2018 12:55 PM > 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
