Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
Intel 730, all the way! Also, avoid the Samsung 840, 840 EVO, 850, and 850 EVO. There is a problem with the 840 and the 840 evo, and it looks like it's the TLC nand. Since the 850 and the 850 EVO are TLC nand (though stacked vertically), I was be super hesitant to entrust my data and productivity to these drives.
http://techreport.com/review/27727/some-840-evos-still-vulnerable-to-read-speed-slowdowns
Intel 730, all the way! Also, avoid the Samsung 840, 840 EVO, 850, and 850 EVO. There is a problem with the 840 and the 840 evo, and it looks like it's the TLC nand. Since the 850 and the 850 EVO are TLC nand (though stacked vertically), I was be super hesitant to entrust my data and productivity to these drives.
http://techreport.com/review/27727/some-840-evos-still-vulnerable-to-read-speed-slowdowns
It's interesting that the article is about the 840evo, yet you tell us here that 840, 840evo, 850, and 850evo are all affected.
http://www.anandtech.com/show/8997/...0-evo-performance-another-fix-is-in-the-worksIn October, Samsung released a tool to address a slowdown in 840 EVO Sequential Read speeds reported by a small number of users after not using their drive for an extended period of time. This tool effectively and immediately returned the drive’s performance to normal levels. We understand that some users are experiencing the slowdown again. While we continue to look into the issue, Samsung will release an updated version of the Samsung SSD Magician software in March that will include a performance restoration tool.
As a reminder, the original 840 EVO performance degradation issue was a result of a combination of NAND cell charge decay and NAND management algorithm issues. While NAND cell charge decay is a normal part of NAND operation, it was something Samsung’s more complex TLC NAND was more sensitive to. Meanwhile Samsung’s algorithms, when faced with this decay, erroneously went into an aggressive read-retry state, which is ultimately what lead to the drop in read performance. Samsung’s fix in turn addressed their NAND management algorithm, and at least at the time was thought to be a permanent fix for the issue.
These more recent performance issues and now Samsung’s statement make it clear that the issue is unfortunately not as fixed as Samsung initially thought it would be. At this point Samsung isn’t saying what the root cause of this latest issue is, but it’s likely that this is a continuation of the original issue. In any case the upshot is that Samsung believes the issue can be corrected, however given the last fix it’s not clear whether this next fix will be any more a permanent fix than the last one.