dm-crypt/LUKS performance

2014-11-16 Thread David Fuchs
Hi all, First off, I realize this question has been asked here and elsewhere before, but I can't seem to find any recent relevant numbers on this. I am setting up a system with an Intel octo-core Avoton, which has AES-NI support. After doing some crude benchmarking tests with dd, I am surprised a

Re: dm-crypt/LUKS performance

2014-11-16 Thread Bob Proulx
David Fuchs wrote: > In short, the write speed plummets to around 160 MB/s, as opposed to 270 > MB/s on the naked partition; read speed is at 115 MB/s (slower than writing > - no idea why), as opposed to 465 MB/s on the bare partition. (I've pasted > the results below.) I don't have an immediate a

Re: dm-crypt/LUKS performance

2014-11-16 Thread David Christensen
On 11/16/2014 04:04 PM, David Fuchs wrote: I am setting up a system with an Intel octo-core Avoton, which has AES-NI support. ... The drive in question is a Samsung 840 pro SSD, Which Debian release? Kernel? Motherboard make/ model? CPU model? RAM module(s) make/ model? SSD exact model?

Re: dm-crypt/LUKS performance

2014-11-17 Thread Henrique de Moraes Holschuh
On Sun, 16 Nov 2014, David Fuchs wrote: > I am setting up a system with an Intel octo-core Avoton, which has AES-NI > support. After doing some crude benchmarking tests with dd, I am surprised > about the huge performance penalty that full-disk encryption apparently has > on read/write throughput.

Re: dm-crypt/LUKS performance

2014-11-17 Thread Tixy
On Sun, 2014-11-16 at 18:56 -0800, David Christensen wrote: > That SSD appears to have hardware encryption. So, why dm-crypt? So you can copy/backup/move disks and partitions without worrying about whether you can get access to the result in the future? Because you don't want to trust or rely on

Re: Re: dm-crypt/LUKS performance

2014-11-17 Thread David Fuchs
> Which Debian release? Kernel? Motherboard make/ model? CPU model? RAM module(s) > make/ model? SSD exact model? Defaults? Customizations? My initial post was indeed a little light on details, so here's more info: I'm dealing with a pristine installation of Wheezy. It is running on a Supermicro A1