linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olivier.mallinger@ip-maker.com (Olivier Mallinger - IP Maker)
Subject: Using FIO tool for performance measure
Date: Thu, 23 May 2013 16:29:15 +0200	[thread overview]
Message-ID: <519E27BB.20009@ip-maker.com> (raw)

Hello.

I have a NVMe controller running on FPGA.
I use Linux Fedora 17 as OS with a core 3.8.4.
The driver is loaded at startup and the NVMe device is recognize without 
any problem (/dev/nvme0n1).
I am able to perform read and write I/O commands.

The problem occurs when i tried to use FIO to measure performance 
(Bandwith, latency and IOPS).
I attached my FIO script.
The performance are poor using a PCIeGen2x4 interface. I monitored 
what's happening inside the controller's hardware and everything works 
fine as it spends time waiting for submission tail update...
FIO seems not using well the queue depth and instead of pushing commands 
into the queue, it waits for command's end before sending a new one.
I try different version of FIO without success (2.0.9, 2.0.13 and 2.0.15).

Did someone already experiment such problem using FIO ? Is there any 
missing option inside my script ?

Thanks for your help.
Regards,
Olivier.
-------------- next part --------------
[global]
ioengine=libaio
iodepth=32
direct=1
size=32m
filename=/dev/nvme0n1

[seq_rd]
name=seq_rd
rw=read
bs=4k
stonewall

[seq_wr]
name=seq_wr
rw=write
bs=4k
stonewall

[rand_rd]
name=rand_rd
rw=randread
bs=4k
stonewall

[rand_wr]
name=rand_wr
rw=randwrite
bs=4k
stonewall

-------------- next part --------------
A non-text attachment was scrubbed...
Name: olivier_mallinger.vcf
Type: text/x-vcard
Size: 316 bytes
Desc: not available
URL: <http://merlin.infradead.org/pipermail/linux-nvme/attachments/20130523/9829a671/attachment.vcf>

                 reply	other threads:[~2013-05-23 14:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=519E27BB.20009@ip-maker.com \
    --to=olivier.mallinger@ip-maker.com \
    /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).