Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Steve King <stkissteve@gmail.com>
To: fio@vger.kernel.org
Subject: [QUESTION] Incorrect arguments for FIO job?
Date: Wed, 14 Apr 2021 09:38:51 -0400	[thread overview]
Message-ID: <68973b2a-c2a6-e1c0-5990-eb2599a585f1@gmail.com> (raw)

Hi folks - could use some help as I'm not a fio expert....

Short version is an external team is presenting results to me that I 
don't entirely believe. The resulting IOPS & Throughput for 'random 
read' and 'random write' are exactly the same, which makes no logical 
sense.  I'm concerned they have a problem with the arguments used in 
FIO; especially as I notice a typo.

Here is what's being run:
fio --randrepeat=1 --ioengine=libaio --direct=1 --sync=1 
  --name=fio-test --filename=random_50read_50write-.fio  --overwrite=1 
--iodepth=64 --size=1GB --readrite=randrw --rwmixread=50 --rwmixwrite=50 
--bs=16k --runtime=60 --time_based --ramp_time=15  --percentage_random=50

Note typo "readRite...."   But a lot of these arguments seem 
redundant.   Thanks!


             reply	other threads:[~2021-04-14 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 13:38 Steve King [this message]
2021-04-14 14:09 ` [QUESTION] Incorrect arguments for FIO job? Ober, Frank

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=68973b2a-c2a6-e1c0-5990-eb2599a585f1@gmail.com \
    --to=stkissteve@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