From: Jens Axboe <axboe@kernel.dk>
To: "Neto, Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@netapp.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Group reporting with latency and IOPS
Date: Wed, 30 Jan 2013 12:08:03 +0100 [thread overview]
Message-ID: <20130130110803.GS8800@kernel.dk> (raw)
In-Reply-To: <843E15216120C047928F6879B0E2D9240F6D496C@SACEXCMBX02-PRD.hq.netapp.com>
On Wed, Jan 30 2013, Neto, Antonio Jose Rodrigues wrote:
> On 1/29/13 3:32 PM, "Jens Axboe" <axboe@kernel.dk> wrote:
>
> >On Tue, Jan 29 2013, Neto, Antonio Jose Rodrigues wrote:
> >> Jens, sorry to bother you again, but I am trying to apply the I've got
> >>this=
> >> error. Could you please help me how to fix it?
> >
> >I forgot to push a previous change out. Pull again and try applying,
> >should apply without fuzz.
> >
> >--
> >Jens Axboe
> >
>
> Hi Jens,
>
> This is neto from Brazil
>
> How are you?
>
> I applied the patch and everything is working. Here is one example:
>
> Thank you very much
>
> neto
>
> -- Output file
>
> workload: (groupid=0, jobs=20): err= 0: pid=2348: Tue Jan 29 22:51:43 2013
> mixed: io=879352KB, bw=168902KB/s, iops=21112 , runt= 30039msec
> slat (usec): min=3 , max=2296 , avg= 6.81, stdev= 4.62
> clat (usec): min=138 , max=248843 , avg=3619.87, stdev=7906.03
> lat (usec): min=145 , max=248863 , avg=3626.68, stdev=7905.91
> clat percentiles (usec):
> | 1.00th=[ 350], 5.00th=[ 454], 10.00th=[ 516], 20.00th=[ 724],
> | 30.00th=[ 780], 40.00th=[ 820], 50.00th=[ 868], 60.00th=[ 924],
> | 70.00th=[ 1048], 80.00th=[ 3760], 90.00th=[11584], 95.00th=[18304],
> | 99.00th=[39680], 99.50th=[50432], 99.90th=[76288], 99.95th=[90624],
> | 99.99th=[123392]
> bw (KB/s) : min= 864, max= 9088, per=2.43%, avg=4100.05,
> stdev=2630.65
> lat (usec) : 250=0.56%, 500=7.90%, 750=14.84%, 1000=44.16%
> lat (msec) : 2=9.40%, 4=3.46%, 10=7.59%, 20=7.80%, 50=3.77%
> lat (msec) : 100=0.48%, 250=0.03%
> cpu : usr=0.00%, sys=0.00%, ctx=0, majf=0, minf=0
> IO depths : 1=0.1%, 2=0.1%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,
> >=64=0.0%
> submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%,
> >=64=0.0%
> complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%,
> >=64=0.0%
> issued : total=r=634207/w=0/d=0, short=r=0/w=0/d=0
>
> Run status group 0 (all jobs):
> MIXED: io=4954.8MB, aggrb=168902KB/s, minb=168902KB/s, maxb=168902KB/s,
> mint=3
> 0039msec, maxt=30039msec
Excellent. Just need to check whether all cases are handled, then I will
get it committed.
--
Jens Axboe
next prev parent reply other threads:[~2013-01-30 11:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 23:32 Group reporting with latency and IOPS Neto, Antonio Jose Rodrigues
2013-01-29 13:02 ` Jens Axboe
2013-01-29 13:41 ` Neto, Antonio Jose Rodrigues
2013-01-29 13:46 ` Jens Axboe
2013-01-29 13:49 ` Neto, Antonio Jose Rodrigues
2013-01-29 13:54 ` Jens Axboe
2013-01-29 13:58 ` Neto, Antonio Jose Rodrigues
2013-01-29 20:10 ` Jens Axboe
2013-01-29 20:28 ` Neto, Antonio Jose Rodrigues
2013-01-29 20:32 ` Jens Axboe
2013-01-29 20:40 ` Neto, Antonio Jose Rodrigues
2013-01-29 21:16 ` Jens Axboe
2013-01-30 3:54 ` Neto, Antonio Jose Rodrigues
2013-01-30 11:08 ` Jens Axboe [this message]
2013-02-01 6:35 ` Georg Schönberger
2013-02-01 10:13 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130130110803.GS8800@kernel.dk \
--to=axboe@kernel.dk \
--cc=Antonio.Jose.Rodrigues.Neto@netapp.com \
--cc=fio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.