From: m@bjorling.me (Matias Bjørling)
Subject: 4K writes on nvme device vs that on ext4 running on nvme block device
Date: Wed, 01 Oct 2014 10:23:24 +0200 [thread overview]
Message-ID: <542BB9FC.5090507@bjorling.me> (raw)
In-Reply-To: <eedf708ac5b545a2b26ee81b60dd49d3@hioexcmbx06-prd.hq.netapp.com>
On 10/01/2014 08:41 AM, Bhattacharya, Indranil wrote:
> Hi,
>
> I was recently doing some experiments using the nvme emulator (nvmeqemu) and I observed a curious thing. There was a marked degradation in write-throughput when I run FIO (multithreaded, O_DIRECT writes) on an ext4 filesystem that has been created on top of a nvme block device; as compared to the same tests which run directly on the nvme block device (i.e. without the filesystem in between).
>
> I plan to repeat this test on a real nvme device as soon as I get one, but some insight from others on the following questions will be helpful:
>
> 1) Have others seen the same on a real nvme device?
Here's my results from an Intel DC P3700. 4k Random Writes, libaio,
qdepth 16 and two jobs.
Plain
112.556 IOPS
~140us completion time
With ext4
112.267 IOPS
~140us completion time
> 2) If yes, any possible explanation for the same?
ext4 does some background work in the beginning if lazy inode table init
and lazy journal init have been enabled during mkfs. This might be what
influence your results.
next prev parent reply other threads:[~2014-10-01 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 6:41 4K writes on nvme device vs that on ext4 running on nvme block device Bhattacharya, Indranil
2014-10-01 8:23 ` Matias Bjørling [this message]
2014-10-05 14:23 ` Bhattacharya, Indranil
2014-10-06 10:34 ` Matias Bjørling
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=542BB9FC.5090507@bjorling.me \
--to=m@bjorling.me \
/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