Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Georg Schönberger" <gschoenberger@thomas-krenn.com>,
	fio@vger.kernel.org
Subject: Re: SSD write latency lower than read latency
Date: Mon, 15 Dec 2014 08:15:33 -0700	[thread overview]
Message-ID: <548EFB15.8080704@kernel.dk> (raw)
In-Reply-To: <2028599731.63796.1418644100540.JavaMail.zimbra@thomas-krenn.com>

On 12/15/2014 04:48 AM, Georg Schönberger wrote:
> Hi Fio users and Jens,
>
> I am currently analyzing read and write latencies of Solid State Disks (SSDs). My assumption was that
> write latencies are usually higher than read latencies. But my tests with Fio on an Intel DCS3500 show
> that average latency while writing is lower than while reading (using fio-2.1.3):
>
> * $ sudo /usr/bin/fio --rw=randrw --name=intelDCS3500 --bs=4k --direct=1 --filename=/dev/sda --rwmixread=0
>      --numjobs=1 --ioengine=libaio --runtime=60 --iodepth=1 --time_based
>      [...]
>      lat (usec): min=30, max=1010, avg=43.32, stdev= 3.42
>      [...]
> * $ sudo /usr/bin/fio --rw=randrw --name=intelDCS3500 --bs=4k --direct=1 --filename=/dev/sda --rwmixread=100
>      --numjobs=1 --ioengine=libaio --runtime=60 --iodepth=1 --time_based
>      [...]
>      lat (usec): min=103, max=2315, avg=121.92, stdev=11.02
>
> I have made this observation on two different machines with different SSDs, always producing similar results.
> Am I doing anything wrong with my tests?
> Are write latencies in general lower than read latencies?
>
> One guess I have is a SSD cache to enhance write access (in particular the Intel datacenter SSDs, as they have
> a "Enhanced power-loss data protection" feature).

Your guess is exactly right, that's what most flash based devices (worth 
their salt) do. That's also why sync write latencies are mostly 
independent of the type of nand used, whereas the read latency will 
easily reflect that.

-- 
Jens Axboe



  reply	other threads:[~2014-12-15 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <298214297.62025.1418642489614.JavaMail.zimbra@thomas-krenn.com>
2014-12-15 11:48 ` SSD write latency lower than read latency Georg Schönberger
2014-12-15 15:15   ` Jens Axboe [this message]
2014-12-17  0:49     ` Matthew Eaton
2014-12-17 10:14     ` Erwan Velu
2014-12-17 15:00       ` Jens Axboe
2014-12-20  8:26         ` Georg Schönberger
2014-12-20 16:38           ` Alireza Haghdoost
2014-12-20 19:33           ` Jens Axboe

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=548EFB15.8080704@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=gschoenberger@thomas-krenn.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