This project has moved and is read-only. For the latest updates, please go here.

M.2 SSD performance issues


Hey guys,

first of all a huge thank you to Mounir for his work on extending and surpassing TrueCrypt.

I've been using VC for quite some time now and I've always been happy with all of the features I used but I've hit some performance issues lately and wanted to ask if there's a chance of getting a fix. I'd also be happy to volunteer to test any possible fixes.

I recently bought a Samsung SSD 960 Evo and benchmarked it with AS SSD Benchmark, did a full encryption of the system drive with AES and benchmarked it again.

The performance has degraded considerably as seen in the pics. Before encryption (read on the left, write on the right):


After encrpytion:


In theory performance of AES should/could be much better:


Sequential read performance has dropped by about 75%, sequential write speeds stayed pretty good (less than -10%).
4k read performance went down by 40%, as did 4k writes.
4k 64 thread read performance lost an amazing 97%, writes still lost about 80%.
Read access times went up by nearly 600%, write access times by 25%. Not sure if there is a relation to read performance in general here but i think there might be.

I'm thinking about switching off VeraCrypt for the 960 EVO system SSD and instead using the Samsung built-in AES encryption, but I trust VeraCrypt more than Samsung and I enjoy system favorite volume automounts, which i think requires a VC-encrypted system drive.

Any ideas how to improve the speed?


My PC for reference:
Asrock Fatality Z170 Professional Gaming i7
Intel Core i7 6700k
4x8GB G-Skill DDR4 3200
5x 8TB Samsung Archive HDD v2
2x Samsung SSD 850 Evo in RAID0 (which always gave me at least an estimated 80% of raw performance after encryption)
Samsung SSD 960 Evo 1TB
Win10 Pro x64


ceroni wrote Jan 29 at 7:21 PM

I think this drive already has hardware based encryption.
From the data sheet
The 960 EVO provides the same data encryption features as other Samsung SATA SSDs. Self-Encrypting Drive (SED) security technology will help keep data safe at all times. It includes an AES 256-bit hardware based encryption engine to ensure that your personal files remain secure. Being hardware-based, the encryption engine secures your data without performance degradation that you may experience with a software-based encryption. Also, the 960EVO is compliant with advanced security management solutions (TCG Opal).

AdamDoe wrote Jan 30 at 4:54 PM

Thanks for the reply but I'm aware of that, I just figured I should do my part in getting VeraCrypt updated to be able to deal with modern SSDs.

But I can understand if Mounir's hands are full - I often don't feel like coding in my spare time after a long day coding at work either.

So I'll guess I'll be switching to the Samsung/ATA encryption thing for the time being.

Regardless, thanks again a whole lot for VC and for keeping TC alive in the first place!

AdamDoe wrote Jan 30 at 5:57 PM

Hah, well, "luckily" I just deleted a huge VeraCrypt container file by accident so I'll be dealing with restoring what was lost there for the next few days. Luckily at least one old backup exists and what was lost can largely be downloaded again.

The theoretical upside of this whole thing however is, of course, that I'll be too busy to deal with the SSD so if any solutions/ideas should come up in the meantime i'll still be able to test :P Anything for science!

AdamDoe wrote Mar 5 at 11:48 PM


I still haven't tried the bullshit Samsung-NSA-backdoored fake-encryption. Any chance to get this solved?