Linux RAID subsystem development
 help / color / mirror / Atom feed
From: pg@lxra2.for.sabi.co.UK (Peter Grandi)
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Intel SSD or other brands
Date: Thu, 29 Dec 2016 17:33:17 +0000	[thread overview]
Message-ID: <22629.18653.431222.163351@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <CAANLjFo4tP9Xdv8JX5waNOu_34zWDKsQqOru3fpt2wOAJuZYcQ@mail.gmail.com>

> [ ... ] sync=1 really differentiates drives and you really
> find which drives are better. [ ... ]

It is not necessarily "better" in a strict sense: flash SSD
devices with supercapacitor-backed persistent caches can be much
faster on 'fsync' heavy workloads, but also cost a lot more
(probably mostly because of market segmentation). Of course
especially on a RAID5 set with lots of read-modify-write.

It is a different performance envelope, not necessarily a
"better" one. If one does not need small-write speed then
cheaper drivers are more appropriate.

However devices which don't have persistent caches and still
have high 'sync=1'/'direct=1' speed because they don't implement
'fsync' synchronously are definitely worse, in the sense of
having arguably no performance at all.

Some manufacturers think that using an SLC cache helps without a
persistent-ed RAM cache, but the persistent=-ed RAM seems a lot
better to me.

  reply	other threads:[~2016-12-29 17:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29  2:14 Intel SSD or other brands Adam Goryachev
2016-12-29 11:39 ` Peter Grandi
2016-12-29 14:35   ` Adam Goryachev
2016-12-29 17:46     ` Peter Grandi
2016-12-29 16:56 ` Robert LeBlanc
2016-12-29 17:33   ` Peter Grandi [this message]
2016-12-29 18:37     ` Peter Grandi
2016-12-29 23:04   ` Adam Goryachev
2016-12-29 23:20     ` Robert LeBlanc
2016-12-29 18:50 ` Doug Dumitru
2016-12-29 22:51   ` Adam Goryachev
2016-12-30  1:24     ` Doug Dumitru
2016-12-30 16:32       ` Pasi Kärkkäinen
2016-12-30 18:23         ` Doug Dumitru
  -- strict thread matches above, loose matches on Subject: below --
2016-12-29  1:52 Adam Goryachev

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=22629.18653.431222.163351@tree.ty.sabi.co.uk \
    --to=pg@lxra2.for.sabi.co.uk \
    --cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox