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: Tue, 29 Jan 2013 14:54:01 +0100 [thread overview]
Message-ID: <20130129135401.GG8800@kernel.dk> (raw)
In-Reply-To: <843E15216120C047928F6879B0E2D9240F6D26D5@SACEXCMBX02-PRD.hq.netapp.com>
On Tue, Jan 29 2013, Neto, Antonio Jose Rodrigues wrote:
> On Tue, Jan 29 2013, Neto, Antonio Jose Rodrigues wrote:
> > atency: (clat) 577usecs - 0.577ms
> > >
> > >Correct too.
> > >
> > >> Am I doing the correct analysis?
> > >
> > >Yep.
> > >
> > >> One question is: Is it possible to have global IOPS and latency?
> > >
> > >You mean for both read and write combined? Fio does not report that,
> > >but for IOPS you could just add them. For latency, the larger of the two.
> > >
> > >--=20
> > >Jens Axboe
> > >
> >
> > Hi Jens
> >
> > This is neto from Brazil
> >
> > How are you?
> >
> > Thank you so much for your answer.
> >
> > How can I have a combined IOPS reported?
>
> You can't, at least not automatically. You would have to sum them up. It would not be hard to add at all, though, controlled by an option. I haven't had any requests for it before now, usually people ask for more fine grained metrics, not the other way around :-)
>
> --
> Jens Axboe
>
> Thank you Jens, I understand. To have an option to group everything
> could be a good thing especially when you are doing a POC or
> demonstrating performance for a customer where they are interested in
> how many IOPS and total latency :-)
I agree, I can see the use case. I'll add a 'unified_rw_reporting'
option to be able to do that. Most accounting is done collectively, so
it should be pretty simple to do this.
--
Jens Axboe
next prev parent reply other threads:[~2013-01-29 13:54 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 [this message]
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
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=20130129135401.GG8800@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.