Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Edoardo Comar <ECOMAR@uk.ibm.com>
Cc: fio@vger.kernel.org
Subject: Re: latency measurements when adding thinktime
Date: Fri, 17 May 2013 12:43:05 +0200	[thread overview]
Message-ID: <20130517104305.GW697@kernel.dk> (raw)
In-Reply-To: <20130517102244.GV697@kernel.dk>

On Fri, May 17 2013, Jens Axboe wrote:
> On Fri, May 17 2013, Edoardo Comar wrote:
> > Hi Jens,
> > 
> > thanks a lot, I tried your suggestion straight away: 
> > The cpu line in the output shows that the job has not been idle at all.
> > but even with thinktime_spin, the latency stays high at at 150ms.
> > 
> > Note also that if I increase thinktime & thinktime_spin by another 10000 
> > us
> > to a total of 20000, then the reported latency goes up another 150ms to a 
> > total of 300ms.
> > Could this be a bug?
> 
> It certainly could. Let me take a look here and see if I can reproduce
> it.

And it was... Basically the same issue that was fixed for rate limiting.
When going to sleep or spinning, ensure that we have all IOs flushed.
Otherwise we could unfairly attribute the sleep towards the completion
latencies.

Fixed here:

http://git.kernel.dk/?p=fio.git;a=commit;h=002e7183cb86d6100efef690b6fa90bf0988b084

or just git pull and you'll get the fix.

-- 
Jens Axboe


  parent reply	other threads:[~2013-05-17 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  0:00 latency measurements when adding thinktime Edoardo Comar
2013-05-17  7:47 ` Jens Axboe
2013-05-17  9:24   ` Edoardo Comar
2013-05-17 10:22     ` Jens Axboe
2013-05-17 10:38       ` Edoardo Comar
2013-05-17 10:43       ` Jens Axboe [this message]
2013-05-17 10:48         ` Edoardo Comar
2013-05-17 10:50           ` Jens Axboe
2013-05-17 10:48         ` 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=20130517104305.GW697@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=ECOMAR@uk.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox