All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Erwan Velu <erwan@seanodes.com>
Cc: fio@vger.kernel.org
Subject: Re: Help required to understand fio output
Date: Wed, 19 Nov 2008 14:43:13 +0100	[thread overview]
Message-ID: <20081119134313.GF26308@kernel.dk> (raw)
In-Reply-To: <492417BC.1020701@seanodes.com>

On Wed, Nov 19 2008, Erwan Velu wrote:
> Jens Axboe wrote:
> 
> [...]
> >The output could do with a bit of prettying up... It's explained in the
> >documentation, though, The 100=64.24% field means that 64.24% of the ios
> >completed within 50 and 99ms, as you indicate.
> >  
> I would say that [50-99]=64.24% would have been less confusing even if 
> it take more room.
> [...]

That's the primary problem, but I guess it's just to compressed for its
own good...

> >>And then, how should I understan lines 8 & 9 that reports that 100% of 
> >>IOs were completed with a depth=4... What happened ?
> >>    
> >
> >Same deal, 4 means 1-4 completions per io_getevents() call for your test
> >case. So any attempt to retrieve completed IO from the system resulted
> >in a return of 1-4 ios.
> I just don't understand what the reason of that 64 -> 4 depth reduction. 
> Is that related to the storage or the kernel capabilities ?

If you don't tell fio otherwise, it'll attempt to reclaim completed IO
as soon as it can. You can control this behaviour with the iodepth_*
options.

-- 
Jens Axboe


      reply	other threads:[~2008-11-19 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 13:15 Help required to understand fio output Erwan Velu
2008-11-19 13:19 ` Jens Axboe
2008-11-19 13:42   ` Erwan Velu
2008-11-19 13:43     ` Jens Axboe [this message]

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=20081119134313.GF26308@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=erwan@seanodes.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.