From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Niels de Carpentier" Subject: Re: Encryption implementation like ZFS? Date: Sat, 31 Dec 2011 18:12:42 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: linux-btrfs@vger.kernel.org To: "Sandra Schlichting" Return-path: In-Reply-To: List-ID: >> ... 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