The Samsung SSD 850 EVO mSATA/M.2 Review
by Kristian Vättö on March 31, 2015 10:00 AM ESTIdle Power Consumption
Since we truncuate idle times to 25µs in our Storage Bench traces, they don't give a fully accurate picture of real world power consumption as idle power consumption is not taken properly into account. Hence I'm still reporting idle power consumption as a separate benchmark because it's one of the most critical metrics when it comes evaluating an SSD for mobile use.
Unfortunately I still don't have a way to test DevSleep power consumption due to lack of platform support, but my testbed supports HIPM+DIPM power commands (also referred to as Slumber power), so the results give a rather accurate picture of real-world idle power consumption.
All Samsung's recent SSDs have had excellent idle power consumption and the 850 EVO mSATA/M.2 is no exception.
TRIM Validation
The move from Windows 7 to 8.1 introduced some problems with the methodology we have previously used to test TRIM functionality, so I had to come up with a new way to test. I tested a couple of different methods, but ultimately I decided to go with the easiest one that can actually be used by anyone. The software is simply called trimcheck and it was made by a developer that goes by the name CyberShadow in GitHub.
Trimcheck tests TRIM by creating a small, unique file and then deleting it. Next the program will check whether the data is still accessible by reading the raw LBA locations. If the data that is returned by the drive is all zeros, it has received the TRIM command and TRIM is functional.
And TRIM appears to be working fine.
Facebook
Twitter
RSS
58 Comments
View All Comments
WackyDan - Saturday, April 4, 2015 - link
Eh... Nope. These won't work in the ThinkPads.blanarahul - Tuesday, March 31, 2015 - link
Hopefully, this drive will put an end to the mSATA/M.2 versions of the 840 non-EVO that companies are shipping in their laptops.Samus - Tuesday, March 31, 2015 - link
DoH! I just paid $20 more for the M550 (basically the MX100) 512GB M2 drive, which is double-sided and needs to be crammed into my laptop :\kgh00007 - Tuesday, March 31, 2015 - link
Hey, is there any chance you could fill one of these m.2 drives with data, power it off for a month then check the read speeds when you power it back on?I need some sort of evidence that this TLC V-nand does not have the same issues as the TLC in the 840 EVO.
Otherwise I'm not going to be able to buy one of these!
Cheers!
goodyes - Wednesday, April 1, 2015 - link
What the hell does not the charts compares with 840 ev msata ? Bad numbers Why not true sequential test ??And this site posting SUCKS, Why in the world I cannot use my facebook or so login, Did you know about disquss ? Get out the absurd captcha that fucking me 30 times or so trying to get a magical potion to know what the words saying,. THIS IS NOT ADVANCE IN TECH THIS IS TRASH
Kristian Vättö - Wednesday, April 1, 2015 - link
This is the third review with the new 2015 SSD Suite and I've only had limited time to test drives, hence the lack of 840 EVO in the graphs.goodyes - Wednesday, April 1, 2015 - link
Ya, but results that I have a 1TB 840 msata and write sequential at more than 500MBps around 520max MBps, and now I see than new 850 msata tops at ?? 480MBps ?? cannot be possible what my eyes look, AND WHY THE HELL NO ONE REVIEWER COMPARE With olders 840 msata, so I must think that all of you guys are a paid reviewers and you get money from samsung, if not, YOU MUST compare to older modelcgorange - Wednesday, April 1, 2015 - link
Other than providing samples, I can assure you that Samsung doesn't pay Anandtech to review its productsEkitrak - Wednesday, April 1, 2015 - link
The Final Words page has 2 entries of "Samsung 840 EVO mSATA" on the Amazon Price Comparison. I'm guessing this is an error and one of them is supposed to be the Sata III version?Kristian Vättö - Wednesday, April 1, 2015 - link
I'm not seeing this -- maybe you accidentally mixed up the 850 EVO mSATA and 840 EVO mSATA as they are both in the table (or maybe this was already fixed by another editor).