fio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Thomas Schneider <74cmonty@gmail.com>, fio@vger.kernel.org
Subject: Re: Using fio with adjusted parameters for use case "DB"
Date: Tue, 7 Mar 2023 10:22:39 -0500	[thread overview]
Message-ID: <c048da7e-ab6d-0209-52b9-5d4262658ab0@gmail.com> (raw)
In-Reply-To: <1e123883-b2c0-ed9f-7242-49f6c3d5bc44@gmail.com>

On 3/7/23 09:30, Thomas Schneider wrote:
> Hello,
> 
> I want to benchmark different storage devices with an I/O workload 
> generated by the "real" application: DB.
> 
> A typcial command could be:
> fio --name=random-writers --ioengine=libaio --iodepth=4 --rw=randwrite 
> --bs=1024 --direct=1 --size=64m --numjobs=2 runtime=120s
> 
> The question is regarding parameters size and runtime:
> - What value should be used for size? Should this be the same as 
> allocated disk space by DB data files? Or just a (reasonable) portion of 
> this? DB data files could be up to xTB.
> - Is it advisable to use runtime? If yes, would this somehow contradict 
> to size, means if I use a larger size, then runtime is obviously longer.
> 

The documentation for runtime is here:

https://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-runtime

Fio will write within the LBAs bounded by offset and size and stop when 
it has touched all the LBAs or when runtime is attained. Run some 
experiments with --debug=io to better understand fio's behavior.

Also take a look at the example job files for help:

https://github.com/axboe/fio/tree/master/examples

Vincent


  reply	other threads:[~2023-03-07 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 14:30 Using fio with adjusted parameters for use case "DB" Thomas Schneider
2023-03-07 15:22 ` Vincent Fu [this message]
2023-03-08 13:46   ` Thomas Schneider
  -- strict thread matches above, loose matches on Subject: below --
2023-03-02  9:49 74cmonty

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=c048da7e-ab6d-0209-52b9-5d4262658ab0@gmail.com \
    --to=vincentfu@gmail.com \
    --cc=74cmonty@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;
as well as URLs for NNTP newsgroup(s).