Obsessed with technology?
Subscribe to the latest tech news as well as exciting promotions from us and our partners!
By subscribing, you indicate that you have read & understood the SPH's Privacy Policy and PDPA Statement.
Product Listing

Samsung SSD 960 Evo: The PCIe SSD mainstream champion

By Kenny Yeo - 22 Jan 2017
Launch SRP: S$349

AS SSD Results

AS SSD 1.8.5636.36856 Results

AS SSD is a benchmark that uses non-compressible and completely random data. This benchmark is useful because some controllers, like the once popular but now defunct SandForce SF-2281, compress data first before moving them around. However, with non-compressible and random data, controllers cannot compress the data first, which forces them to deal with data as they are. Therefore, this is a useful benchmark to prevent drivers using controllers like the SF-2281 controller or similar from gaining an upper hand.

On AS SSD’s Copy benchmark, the SSD 960 Evo was comfortably faster than the OCZ RD400 and Plextor M8Pe. It was a good match for the SSD 950 Pro as well, besting it on the ISO and Game workloads. The SSD 960 Pro was the fastest drive overall in this benchmark.

The SSD 960 Evo proved to have very fast sequential performance as its sequential read and write speeds were beyond every drive, other than the SSD 960 Pro. Yes, the SSD 960 Evo even outpaced the SSD 950 Pro. 

Its performance on the 4K and more intensive 4K, 64 queue depth workloads were equally impressive. On the 4K workload, the SSD 960 Evo held its own and recorded very respectable numbers. And on the 4K, 64 queue depth workload, its performance was even more impressive as it came very close to the SSD 960 Pro and easily outperformed all the other drives.


  • Performance 9
  • Features 8.5
  • Value 9.5
The Good
Incredible performance for a TLC NAND SSD
High endurance for TLC NAND SSD
Supports latest interface and NVMe protocol
Attractively priced
Includes drive management and data migration tools
The Bad
Only comes in M.2 form factor
Performance dips once TurboWrite cache is exhausted