From: Stan Hoeppner <stan@hardwarefreak.com>
To: Derek Piper <derek.piper@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: How-to for enabling TRIM for SSD RAID-1 arrays?
Date: Fri, 13 Sep 2013 17:54:54 -0500 [thread overview]
Message-ID: <523397BE.8080404@hardwarefreak.com> (raw)
In-Reply-To: <CAD2NviVyoF4y9uQnvcng082zAGQoXq18JT7WM=+RfBGCzCp9zA@mail.gmail.com>
On 9/13/2013 3:25 PM, Derek Piper wrote:
> Having found a posting on this list from July this year, I am trying to
> find if (and how) TRIM support is supported and enabled under RAID 1 with 2
> SSD drives.
The are more important questions to first ask yourself.
1. Will TRIM benefit your make/model of SSDs?
Are they the same brand, model, and firmware? If different brands
or models, or even the same model w/different firmware, the two may
behave completely differently WRT TRIM. One may speed up while the
other slows down.
2. Will it benefit your workloads?
3. How compressible are your files, on average?
4. Which SSDs? SandForce 22xx based? Which firmware rev? See:
http://www.anandtech.com/show/6107/corsair-force-series-gs-240gb-review
5. Do you plan to use realtime discard or batch discard? Most recent
data shows that realtime discard murders performance.
Summary: There is much, much, more to optimizing SSD performance than
getting TRIM working down the stack. In fact some SSDs work better
without TRIM, and some perform worse when TRIM is used.
For many users, TRIM is a solution to a problem they may never have.
They simply want it because they've read somewhere that they should have it.
--
Stan
next prev parent reply other threads:[~2013-09-13 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 20:25 How-to for enabling TRIM for SSD RAID-1 arrays? Derek Piper
2013-09-13 20:36 ` Roberto Spadim
2013-09-13 20:48 ` Roberto Spadim
2013-09-13 22:54 ` Stan Hoeppner [this message]
2013-09-14 3:53 ` Derek Piper
2013-09-14 7:04 ` Mikael Abrahamsson
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=523397BE.8080404@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=derek.piper@gmail.com \
--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 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.