From: "Niels de Carpentier" <niels@decarpentier.com>
To: "Sandra Schlichting" <littlesandra88@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Encryption implementation like ZFS?
Date: Sat, 31 Dec 2011 18:12:42 +0100 [thread overview]
Message-ID: <d5b5f4fe2e07a326f88bd228290e518b.squirrel@webmail.decarpentier.com> (raw)
In-Reply-To: <CAELiMBOzsZazJsWKA7ZqcBTF4DyrFGDo0=fdvW7X8WaaN1p7bw@mail.gmail.com>
>> ... and depending on which SSD you use, it shouldn't matter. Really.
>>
>> Last time I tried with sandforce SSD + btrfs + -o discard, forcing
>> trim actually made things slower. Sandforce (and probably other modern
>> SSD) controllers can work just fine even without explicit trim fs
>> support.
>
> What command did you use to test this?
>
> I have an OCZ Agility 3 SSD, which have the latest Sandforce
> controller, so I would really like to try reproduce your test setup.
Ok, the sandforce controller makes things interesting.
First of all, sandforce controllers have a very high failure rate, so make
sure you have backups!!
Sandforce controllers also use compression and deduplication to increase
performance. Encryption will make your data incompressible and random, so
this can have a big impact on performance, depending on the
characteristics of your data.
Sandforce controllers also have life time throttling, which will throttle
writes heavily if it thinks you will wear out the flash within the
warranty period. If you have a very heavy write workload this can be an
issue.
If you don't have a working trim it is a good idea to leave part of your
drive unused. (Make sure you either do this after a full write erase of
the drive, or do a manual trim of that area, otherwise it won't work).
This will make sure the drive has enough spare sectors to do garbage
collection and can greatly improve performance if your drive is full.
Niels
next prev parent reply other threads:[~2011-12-31 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 18:32 Encryption implementation like ZFS? Sandra Schlichting
2011-12-30 19:27 ` Billy Crook
2011-12-30 20:12 ` Sandra Schlichting
2011-12-30 20:49 ` Billy Crook
2011-12-30 21:12 ` Sandra Schlichting
2011-12-31 9:53 ` Felix Blanke
2011-12-31 14:12 ` Sandra Schlichting
2011-12-31 9:53 ` Fajar A. Nugraha
2011-12-31 14:00 ` Sandra Schlichting
2011-12-31 17:12 ` Niels de Carpentier [this message]
2011-12-31 23:04 ` Fajar A. Nugraha
2012-01-01 15:22 ` Niels de Carpentier
2011-12-31 16:01 ` Edward Ned Harvey
2011-12-30 22:10 ` Tomasz Torcz
2011-12-31 3:36 ` Niels de Carpentier
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=d5b5f4fe2e07a326f88bd228290e518b.squirrel@webmail.decarpentier.com \
--to=niels@decarpentier.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=littlesandra88@gmail.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;
as well as URLs for NNTP newsgroup(s).