The Samsung SSD 850 EVO mSATA/M.2 Review
by Kristian Vättö on March 31, 2015 10:00 AM ESTSequential Read Performance
Our sequential tests are conducted in the same manner as our random IO tests. Each queue depth is tested for three minutes without any idle time in between the tests and the IOs are 4K aligned similar to what you would experience in a typical desktop OS.
In sequential read performance the difference between drives is rather marginal, but in power consumption we start to see some differences. At 250GB and 120GB the 850 EVO is very efficient, but the 500GB and 1TB are again more power hungry.
Looking at performance across all queue depths doesn't reveal any surprises: at QD2 and higher all drives are practically saturating the SATA 6Gbps interface. What's notable, though, is that the 1TB degrades in performance as the queue depth increases. I wonder if this is a thermal issue (mSATA/M.2 don't have a chassis to use as a heatsink) or just poor firmware optimization.
 |
|||||||||
Sequential Write Performance
Sequential write testing differs from random testing in the sense that the LBA span is not limited. That's because sequential IOs don't fragment the drive, so the performance will be at its peak regardless.
In sequential write speed the capacity plays a more significant role because the 120GB and 250GB are noticeably behind the 500GB and other higher capacity drives. The poor performance of the 1TB model is once again a surprise, though.
The full graph of all queue depths shows the reason for the 1TB's low performance: it starts high at ~430MB/s, but after that the performance decreases.
 |
|||||||||
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).