All of
 help / color / mirror / Atom feed
From: Damien Le Moal <>
To: Robert Balogh <>, fio <>
Subject: Re: FIO performance measurement between volumes
Date: Fri, 14 Jan 2022 08:20:31 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 1/13/22 20:47, Robert Balogh wrote:
> hello FIO experts,
> I am a beginner in FIO, and I met with a problem.
> Currently in my Ubuntu based server the "/dev/vdb1" volume is attached
> to the "/home/batman/fio/cindervolume" path. FIO job is configured
> like this
>     [global]
>     filename=fio-172_20_2_13
>     directory=/home/batman/fio/cindervolume rw=rw
>     rwmixread=60
>     rwmixwrite=40
>     bs=4k
>     rate=500k
>     direct=1
>     numjobs=1
>     time_based=1
>     runtime=14d
>     verify=crc32c
>     continue_on_error=all
>     group_reporting=1
>     [file1]
>     iodepth=1
>     ; -- end job file --
> FIO is started like this and works well:
>     /usr/bin/fio --size=10G
> --output=/home/batman/fio/cindervolume/fio-172_20_2_13-process.log
> /home/batman/fioApp/fio-seq-RW.job &
> FIO version I use: fio-3.25
> My next step would be to attach a 2nd volume for example "/dev/vdc" to
> "/home/batman/fio/cindervolume-2" path, and I would do performance
> measurement between the volumes. I was checking the FIO user’s guide,
> but unfortunately I
> cannot figure out which parameter might help me to solve this topic.
> By-the-way is this possible to do with FIO? If so, could you please
> help me by giving some direction/hints?

Move the directory=/... option from global section into the job section
and add a job for your other volume with directory= again added in that
job section to point to the new volume directory. The 2 jobs will run
simultaneously targetting different volumes, unless you add "stonewall",
in which case the jobs will run one after the other.

Or you could just write another fio script for the second volume.

It is not clear if you want to run the perf tests on the 2 volumes in
parallel or one after the other.

> thanks for your help,
> /Robi

Damien Le Moal
Western Digital Research

  reply	other threads:[~2022-01-13 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 11:47 FIO performance measurement between volumes Robert Balogh
2022-01-13 23:20 ` Damien Le Moal [this message]
2022-01-14  7:47   ` Robert Balogh
     [not found]     ` <>
2022-01-17  7:48       ` Robert Balogh

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.