All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Nick Neumann <nick@pcpartpicker.com>, fio@vger.kernel.org
Subject: Re: A fio job that just waits?
Date: Thu, 27 Jan 2022 08:41:39 +0900	[thread overview]
Message-ID: <83721719-aeb7-2a64-2cd2-ccc9b5b2113e@opensource.wdc.com> (raw)
In-Reply-To: <CADqNVTpfbX2WiuzUxap5iOEaBJV0H7nup7b78acd9BAin4DAfA@mail.gmail.com>

On 2022/01/27 8:08, Nick Neumann wrote:
> Is there a clean way to create a fio job that just waits for a fixed
> time period? I'm fairly new to fio, and want a delay between two
> consecutive jobs. I use "wait_for" to serialize as needed, and
> expected "startdelay" to allow me to put the desired delay between the
> two. But it looks like the startdelay for a job begins when fio starts
> and not when the job referenced in a "wait_for" finishes.

The job that needs to be started after a delay should have both wait_for and
startdelay options. That should work.

> 
> I can play games with a job with a very low bandwidth limit (e.g.
> 1B/s) and "runtime" and "time_based", but it feels hacky.
> 
> Am I thinking about how to get a delay between two jobs wrong? Is
> there a better way? I realize I could just run fio multiple times with
> command line delays between the runs, but I'd like the results of the
> runs to share the same time basis and output/log files.
> 
> Thanks,
> Nick


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2022-01-26 23:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 23:08 A fio job that just waits? Nick Neumann
2022-01-26 23:41 ` Damien Le Moal [this message]
2022-01-28 17:02   ` Nick Neumann
2022-01-29  0:16     ` Damien Le Moal
2022-01-29  6:52       ` Nick Neumann
2022-01-31 18:18         ` Nick Neumann
2022-01-27 14:03 ` Erwan Velu
2022-01-28 17:11   ` Nick Neumann
2022-01-28 23:09     ` Nick Neumann

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=83721719-aeb7-2a64-2cd2-ccc9b5b2113e@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=fio@vger.kernel.org \
    --cc=nick@pcpartpicker.com \
    /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.