Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: fio@vger.kernel.org
Subject: Fio high IOPS measurement mistake
Date: Mon, 29 Feb 2016 21:17:21 -0800	[thread overview]
Message-ID: <56D525E1.6010407@vlnb.net> (raw)

Hello,

I'm currently looking at one NVRAM device, and during fio tests noticed that each fio
thread consumes 30% of user space CPU. I'm using ioengine=libaio, buffered=0, sync=0
and direct=1, so user space CPU consumption should be virtually zero.

That 30% user CPU consumption makes me suspect that this is overhead for internal fio
housekeeping, i.e., scientifically speaking, fio instrumental measurement mistake (I
hope, I'm using correct English terms).

Can anybody comment it and suggest how to decrease this user space CPU consumption?

Here is my full fio job:

[global]
ioengine=libaio
buffered=0
sync=0
direct=1
randrepeat=1
softrandommap=1
rw=randread
bs=4k
filename=./nvram (it's a link to a block device)
exitall=1
thread=1
disable_lat=1
disable_slat=1
disable_clat=1
loops=10
iodepth=16

[file1]

[file2]

I'm working on million+ IOPS range.

Thanks,
Vlad

             reply	other threads:[~2016-03-01  5:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  5:17 Vladislav Bolkhovitin [this message]
2016-03-01  6:01 ` Fio high IOPS measurement mistake Sitsofe Wheeler
2016-03-02  4:25   ` Vladislav Bolkhovitin
2016-03-02  7:38     ` Sitsofe Wheeler
2016-03-03  3:02       ` Vladislav Bolkhovitin
2016-03-02 18:37     ` Elliott, Robert (Persistent Memory)
2016-03-03  3:03       ` Vladislav Bolkhovitin
2016-03-03 21:03         ` Elliott, Robert (Persistent Memory)
2016-03-04  4:36           ` Vladislav Bolkhovitin
2016-03-03  3:03     ` Vladislav Bolkhovitin
2016-03-03  7:10       ` Sitsofe Wheeler
2016-03-03  7:13         ` Sitsofe Wheeler
2016-03-04  4:37           ` Vladislav Bolkhovitin
2016-03-03 16:20         ` Jens Axboe
2016-03-04  4:37           ` Vladislav Bolkhovitin
2016-03-04 15:33             ` Jens Axboe
2016-03-05  0:47               ` Vladislav Bolkhovitin
2016-03-05  0:54                 ` Jens Axboe
2016-03-05  1:09                   ` Vladislav Bolkhovitin
2016-03-04  4:37         ` Vladislav Bolkhovitin
2016-03-02  8:26 ` Andrey Kuzmin
2016-03-03  3:02   ` Vladislav Bolkhovitin

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=56D525E1.6010407@vlnb.net \
    --to=vst@vlnb.net \
    --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