Samsung SM951 (512GB) PCIe SSD Reviewby Kristian Vättö on February 24, 2015 8:00 AM EST
AnandTech 2015 Client SSD Suite
The core of our SSD test suite has remained unchanged for nearly four years now. While we have added new benchmarks, such as performance consistency and Storage Bench 2013, in response to the evolution of the SSD industry, we haven't done a major overhaul to take our testing to the next level. That all changes today with the introduction of our 2015 Client SSD Suite.
Just to be clear, there weren't any flaws in the way we did testing in the past -- there were simply some shortcoming that I've been wanting to fix for a while now, but like any big upgrade it's not done overnight. There are four key areas where I focused in the 2015 Suite and these are modernizing our testbed, depth of information, readability and power consumption.
Our old testbed was old, really old. We were using a Sandy Bridge based system with Intel Rapid Storage Technology 10.2 drivers from 2011, so it doesn't take a genius to figure out that our system was desperately in need of a refresh. The 2015 testbed is the latest of the latest with an Intel Haswell CPU and ASUS Z97 motherboard. For the operating system, we have upgraded from Windows 7 to Windows 8.1 with native NVMe driver, which ensures that our setup is fully prepared for the wave of PCIe NVMe SSDs arriving in the second half of 2015. We are also using the latest Intel Rapid Storage Technology drivers now, which should provide a healthy boost over the old ones we were using before. I've included the full specs of the new system below.
|AnandTech 2015 SSD Test System|
|CPU||Intel Core i7-4770K running at 3.5GHz (Turbo & EIST enabled, C-states disabled)|
|Motherboard||ASUS Z97 Deluxe (BIOS 2205)|
|Chipset Drivers||Intel 10.0.24+ Intel RST 18.104.22.1680|
|Memory||Corsair Vengeance DDR3-1866 2x8GB (9-10-9-27 2T)|
|Graphics||Intel HD Graphics 4600|
|Desktop Resolution||1920 x 1080|
|OS||Windows 8.1 x64|
- Thanks to Intel for the Core i7-4770K CPU
- Thanks to ASUS for the Z97 Deluxe motherboard
- Thanks to Corsair for the Vengeance 16GB DDR3-1866 DRAM kit, RM750 power supply, Hydro H60 CPU cooler and Carbide 330R case
The second improvement we have made is regarding the depth of information. Every now and then I found myself in a situation where I couldn't explain why one drive was faster than the other in our Storage Bench tests, so the 2015 Suite includes additional Iometer tests at various queue depths to help us understand the drive and its performance better. I'm also reporting more data from the Storage Bench traces to better characterize the drive and providing new metrics that I think are more relevant to client usage than some of the metrics we have used in the past. The goal of the 2015 Suite is to leave no stone unturned when it comes to explaining performance and I'm confident that the new Suite does an excellent job at that.
However, the increase in depth of information creates a readability problem. I know some of you prefer to have easy and quick to read graphs, but it's hard to present a mountain of data in a format that's convenient to read. To give you the best of both worlds, I'm providing both the easy and quick to read graphs as well as the full data for those who want to dig in a bit deeper. That way the benchmarks will remain comfortable to skim through in case you don't have a lot of time on your hands, but alternatively you will get access to far more data than in the past.
Last but not least, I'm taking power testing to a whole new level in our 2015 Suite. In the past, power consumption was merely a few graphs near to the end of the article and to be honest the tests we ran didn't give the full scope of the drive's power behavior. In our 2015 Suite, power is just as important as performance is because I'm practically testing and reporting power consumption in every benchmark (though for now this is limited to SATA drives). In the end, the majority of SSDs are employed in laptops and power consumption can actually be far more critical than performance, so making power consumption testing a first class citizen makes perfect sense.
A Word About Storage Benches and Real World Tests
While I'm introducing numerous new benchmarks and performance metrics, our Storage Bench traces have remained unchanged. The truth is that workloads rarely undergo a dramatic change, so I had no reason to create a bunch of new traces that would ultimately be more or less the same that we have already used for years. That's why I also dropped the year nomenclature from the Storage Benches because a trace from 2011 is still perfectly relevant today and keeping the year might have given some readers a picture that our testing is outdated. Basically, the three traces are now called The Destroyer, Heavy and Light with the first one being our old 2013 Storage Bench and the two latter ones being part of our 2011 Storage Bench.
I know some of you have criticized our benchmarks due to the lack of real world application tests, but the unfortunate truth is that it's close to impossible to build a reliable test suite that can be executed in real time. Especially if you want to test something else than just boot and application launch times, there is simply too many tasks in the background that cannot be properly controlled to guarantee valid results. I think it has become common knowledge that any modern SSD is good enough for an average user and that the differences in basic web-centric workloads are negligible, so measuring the time it takes to launch Chrome isn't an exciting test to be honest.
In late 2013, I spent a tremendous amount of time trying to build a real world test suite with a heavier workload, but I kept hitting the same obstacle over and over again: multitasking. One of the most basic principles of benchmarking is reproducibility, meaning that the same test can be run over and over again without significant unexplainable fluctuation in the results. The issue I faced with multitasking was that once I started adding background operations, such as VMs, large downloads and backups like a heavier user would have in the background, my results were no longer explainable as I had lost the control of what was accessing the drive. The swings were significant enough that the results wouldn't hold any ground, which is why you never saw any fruit of my endeavors.
As a result, I decided to drop off real world testing (at least for now) and go back to traces, which we have been using for years and know that they are reliable, although not a perfect way to measure performance. Unfortunately there is still no TRIM support in the playback and to speed up the trace playback we've cut the idle times to a maximum of 25 milliseconds. Despite the limitations, I do believe that traces are the best to measure meaningful real world performance because the IO trace is still straight from a real world workload, which cannot be properly replicated with any synthetic benchmark tool (like Iometer).
Post Your CommentPlease log in or sign up to comment.
View All Comments
peevee - Friday, March 20, 2015 - linkIOmeter? Packing several weeks/months of IO into a several minutes/hours test? Seriously, your tests have become SO artificial as not to correspond to any real life experiences at all. For example, in real life SSD write speed almost does not matter, because almost always they are asynchronous - write happens into cache and user does not wait anything, or speed of writes is limited by the speed of data acquisition - case in point, you download test is always limited by much slower internet speed, or copying pictures off camera/SD card are limited by much slower camera/reader, USB or SD speeds etc. Background backup, happening without a user AT ALL? Come on!
It would be actually much more interesting to see at least a few REAL numbers, like good old starting Windows or copying a catalog full of pictures and videos or starting a VM. So the users would see what amount of their time they would REALLY save by investing extra into a faster drive.
kishisaki - Tuesday, April 7, 2015 - linkHow did you get all those speed with Asus Z97 Deluxe?
I thought it only has a 10Gb/s M.2 Slot?
Gradius2 - Wednesday, April 15, 2015 - linkMy solution is WAYYYY cheaper and bigger, I have 670GB (real size) on my little RAID, see the performance: http://i61.tinypic.com/2vt9mo6.jpg
xyvyx2 - Wednesday, July 22, 2015 - linkI was able to keep the temps down on my SM951 by attaching a small heatsink... I need to do some data logging, but I don't think it's gone over 60C since:
stevae - Wednesday, August 12, 2015 - linkwhy isn't there a trouble shoot included IF your result comes back that the drive DOES NOT have trim working? this is incomplete article.
Invisibleman - Sunday, August 16, 2015 - linkKristian,
Because I didn't read this review earlier and I am now planning to upgrade my PC to an M2 SSD. I came to this review.
But there is one thing I realy don't understand. As the setup is saying, you have tested with de Asus Z97 DeLuxe. I know there are 2 different versions of this one. 1 is with USB 3.1 support (new version) and 1 with USB 3.0 (Old one) this one I have.
But if I look at the specs then the Z97 DeLuxe shares the bandwide with SataExpress 1 and have only 2 x PCI Express 3.0/2.0 x 16 Slots (Single at 16x or dual at x8/x8 Mode)
But as I read the SM951 needs to have PCI 3.0 x 4bus. Am I missing something? For me it seems that the SM951 can't run full speed on this board. If it goes thru Sata Express then also get only PCI 3.0 X 2. But in the test (charts) you are mention PCI 3.0 x 4. How is this possible to get if the Max is PCI 3.0 x 2?
So can you tell me what I am missing? What do I need to do/buy extra to get this one run one full power meaning PCI 3.0 x 4.
Hoogmade - Monday, December 7, 2015 - linkWhat card is used to use the SM951 in a Mac Pro 2012?
I tried the Addonics ADM2PX4 but that doesn't seem to work.
dtscaps - Friday, March 11, 2016 - linkOk, this is supposed to be a review to guide me what SSD to buy. I read 10 pages of performance specs and 72 more comments dealing with microseconds marginality. The fact that this drive does or does not have an AES self encrypting mechanism adering to OPAL 2 with a possible IEEE1667 extension IS IMPORTANT. IT IS A COMPLETE SHOW STOPPER if the drive cannot encrypt data. Maybe except if you are a kid playing with new toys.
So, is this SSD self encrypting ?
Does it support Opal 2
Does it support the IEEE1667 extension?