* Using FIO tool for performance measure
@ 2013-05-23 14:29 Olivier Mallinger - IP Maker
0 siblings, 0 replies; only message in thread
From: Olivier Mallinger - IP Maker @ 2013-05-23 14:29 UTC (permalink / 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>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-05-23 14:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-23 14:29 Using FIO tool for performance measure Olivier Mallinger - IP Maker
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).