Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
* 4K writes on nvme device vs that on ext4 running on nvme block device
@ 2014-10-01  6:41 Bhattacharya, Indranil
  2014-10-01  8:23 ` Matias Bjørling
  0 siblings, 1 reply; 4+ messages in thread
From: Bhattacharya, Indranil @ 2014-10-01  6:41 UTC (permalink / raw)


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?
	2) If yes, any possible explanation for the same?

Thanks,
Indranil ???

^ permalink raw reply	[flat|nested] 4+ messages in thread

* 4K writes on nvme device vs that on ext4 running on nvme block device
  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
  2014-10-05 14:23   ` Bhattacharya, Indranil
  0 siblings, 1 reply; 4+ messages in thread
From: Matias Bjørling @ 2014-10-01  8:23 UTC (permalink / raw)


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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* 4K writes on nvme device vs that on ext4 running on nvme block device
  2014-10-01  8:23 ` Matias Bjørling
@ 2014-10-05 14:23   ` Bhattacharya, Indranil
  2014-10-06 10:34     ` Matias Bjørling
  0 siblings, 1 reply; 4+ messages in thread
From: Bhattacharya, Indranil @ 2014-10-05 14:23 UTC (permalink / raw)


Thanks Matias. I don't see much difference in your tests between the two. I used 16 threads in FIO. If you increase the number of threads, do you get a larger difference?

-Indranil

> -----Original Message-----
> From: Matias Bj?rling [mailto:m at bjorling.me]
> Sent: 01 October 2014 13:53
> To: linux-nvme at lists.infradead.org; Bhattacharya, Indranil
> Subject: Re: 4K writes on nvme device vs that on ext4 running on nvme block device
> 
> 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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* 4K writes on nvme device vs that on ext4 running on nvme block device
  2014-10-05 14:23   ` Bhattacharya, Indranil
@ 2014-10-06 10:34     ` Matias Bjørling
  0 siblings, 0 replies; 4+ messages in thread
From: Matias Bjørling @ 2014-10-06 10:34 UTC (permalink / raw)


On 10/05/2014 04:23 PM, Bhattacharya, Indranil wrote:
> Thanks Matias. I don't see much difference in your tests between the two. I used 16 threads in FIO. If you increase the number of threads, do you get a larger difference?
>
> -Indranil
>

With 16 threads, and 64qdepth for each, I get:

Plain: 224787 IOPS and avg. 4484us latency
Ext4:  203671 IOPS and avg. 5008us latency

A couple of percent difference, nothing much.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-10-06 10:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2014-10-05 14:23   ` Bhattacharya, Indranil
2014-10-06 10:34     ` Matias Bjørling

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox