From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@intel.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: REPORT: FIO random read performance degradation without "norandommap" option
Date: Fri, 9 Jan 2015 22:42:03 +0000 [thread overview]
Message-ID: <D0D596A1.FF42%andrey.o.kudryavtsev@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
Colleagues,
I executed 2-hour runs of 4KRR to understand performance changes across the time on the specific very fast NVMe SSD with 1.6TB capacity.
I noticed the side effect of “norandommap” parameter performing full span test on the block device.
Here is the example of the result with random map (I.e. without "norandommap" option) within 120 minutes windows.
[cid:E6872B64-35D1-4447-A0CF-32E6411D9BDB]
(IOPS in blue)
As soon as I enabled “norandommap” option the curve has changed into the straight line as expected.
Some technical details:
I’m running Centos 7 with 3.18 kernel, SSD of course in the precondition state. FIO 2.2.2 (I unfortunately got higher CPU utilization with 2.2.4 which I’ll report separately).
Config file:
[global]
name=4k random read
filename=/dev/nvme0n1
ioengine=libaio
direct=1
bs=4k
rw=randread
iodepth=16
numjobs=8
buffered=0
size=100%
randrepeat=0
norandommap
refill_buffers
group_reporting
[job1]
--
Andrey Kudryavtsev,
SSD Solution Architect
Intel Corp.
[-- Attachment #2: Screen Shot 2015-01-09 at 2.33.53 PM.png --]
[-- Type: image/png, Size: 15762 bytes --]
next reply other threads:[~2015-01-09 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 22:42 Kudryavtsev, Andrey O [this message]
2015-01-09 22:49 ` REPORT: FIO random read performance degradation without "norandommap" option Elliott, Robert (Server Storage)
2015-01-09 23:01 ` Kudryavtsev, Andrey O
2015-01-10 9:20 ` Andrey Kuzmin
2015-01-12 21:06 ` Kudryavtsev, Andrey O
2015-01-12 22:56 ` Elliott, Robert (Server Storage)
2015-01-09 23:07 ` Kulkarni, Vasu
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=D0D596A1.FF42%andrey.o.kudryavtsev@intel.com \
--to=andrey.o.kudryavtsev@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.