All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jens Rosenboom <j.rosenboom@x-ion.de>, Fio <fio@vger.kernel.org>
Subject: Re: [PATCH] Fix ETA calculations
Date: Thu, 19 Nov 2015 13:32:21 -0700	[thread overview]
Message-ID: <564E31D5.6040800@kernel.dk> (raw)
In-Reply-To: <1447944744.32482.13.camel@x-ion.de>

On 11/19/2015 07:52 AM, Jens Rosenboom wrote:
> There are a couple of issues in eta.c:
>
> - The comparison for time- vs. rate-based ETA calculation is done the
>    wrong way round.
> - The elapsed ramp time should only be subtracted when the thread has
>    indeed entered the ramp phase.
> - Currently jobs that are stonewalled are not taken into account for ETA
>    calculation. This patch at least fixes this for the case that there is
>    only a single job per stonewall group.
> ---
>
> This patch tries to fix some issues I have found, this may
> also be related to the ones mentioned earlier in
> http://www.spinics.net/lists/fio/msg04187.html
>
> The part regarding stonewalled jobs may require some further work, but
> at least it gives proper values now for my standard fio runs containing
> just a sequence of singular jobs.

Thanks this is great, I'll get this applied and tested.

> Also, I'm still wondering about the intention behind the way done_secs
> is meant to work. It cumulates time spent in finished jobs globally, but
> is being used in per-job ETA calculations. This seems to break at
> least for the case of stonewalled jobs, too.

The eta output could use some love, no doubt about that. It could easily 
be a lot more clever wrt multiple jobs, fluctuations, etc.

-- 
Jens Axboe



      reply	other threads:[~2015-11-19 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 14:52 [PATCH] Fix ETA calculations Jens Rosenboom
2015-11-19 20:32 ` 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=564E31D5.6040800@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=j.rosenboom@x-ion.de \
    /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.