Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Saeed <ionictea@gmail.com>
To: fio@vger.kernel.org
Subject: Re: fio jobs time_based & runtime scope
Date: Mon, 25 Jul 2016 18:15:29 -0500	[thread overview]
Message-ID: <nn66ih$j66$1@ger.gmane.org> (raw)
In-Reply-To: CALjAwxgP4k4rRFAgpiJ-oBaBHd0OAyXXJ-dTZg7QxyaD36dO_g@mail.gmail.com

Here's the example:

[global]
bs=4k
ioengine=libaio
iodepth=32
size=1g
direct=1
time_based=1
runtime=300
filename=/dev/sdb
group_reporting
numjobs=1

# validation
do_verify=1
verify_fatal=1
verify_dump=1

verify_pattern=0x00000001

[sequential]
rw=readwrite
stonewall

[random]
rw=randrw
stonewall

So with this job file there are two job declarations (sequential & 
random).  Does the time_based & runtime requirement apply to the entire 
job as a whole or per job declaration?

On 2016-07-25 17:13:57 +0000, Sitsofe Wheeler said:

> On 25 July 2016 at 18:00, Saeed 
> <ionictea@gmail.com> wrote:
>> If a job file contains x number of job declarations ([jobxx]) how does the
>> 'time_based" and 'runtime' scoped?
>> 
>> Is it per job declaration or inclusive of all the job declarations in the
>> file?  I'm trying to set a limit in run time to have the jobs run until a
>> certain amount of time has been reached and the jobs still run over the
>> 'runtime' defined limit
> 
> Could you give a minimal job file that demonstrates the problem and
> just to check are you using time_based too
> (https://github.com/axboe/fio/blob/fio-2.13/HOWTO#L1200 )?




  reply	other threads:[~2016-07-25 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 17:00 fio jobs time_based & runtime scope Saeed
2016-07-25 17:13 ` Sitsofe Wheeler
2016-07-25 23:15   ` Saeed [this message]
2016-07-26  6:15     ` Sitsofe Wheeler
2016-07-26 16:53       ` Saeed
2016-07-26 18:11         ` Sitsofe Wheeler
2016-07-27  1:36           ` Saeed

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='nn66ih$j66$1@ger.gmane.org' \
    --to=ionictea@gmail.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