Panic, Chaos, Destruction. My work here is done.
Drink. Get drunk. Fall over - P O'H
OK, I will win to day or my name isn't Ethel Crudacre! - DDEthel Crudacre
I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer
Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
Have they had conformation of the results yet? I'd hate to be the PR guy saddled with the job of explaining it - bet he gets a look that withers from the shareholders! Hopefully it'll spur them on to develop better standards.
Interesting that when the Samsung 840/840Pro series came out they got some negative reviews, like this one on AnandTech: "Samsung Explains The Firmware Bug Causing The Failures of SSD 840/840 Pro" by Kristian Vatto, on 12/7/2012 1:05 PM EST. ... edited to add omitted link ... [^]
I assume the firmware problem with the 840 series has been fixed.
Note that the Samsung 830 256 mb. Series MZ-7PC256B/WW MLC-type SSD is the highest user-rated SSD on NewEgg, currently [^], with 310 user reviews: 87% of verfied owners gave it the highest rating.
"What do humans depend on: words ! We're suspended in language: we can never say what's up: or, down.
We must communicate experience and ideas, but in ways that do not become ambiguous, and lose objectivity.
For parallels in human ideas to quantum theory: we must turn to psychology, or to the paradoxes of being thinkers like Buddha and Lao Tzu illuminated, when trying to grasp reality, as both observer, and actor, in human life's small-scale micro-cosmic drama."
I'll second leppie suggestion. Regular Samsung 840 is using TLC nand which has significantly shorter life span than MLC. And while most likely TLC will outlive the rest of your PC, in my opinion the data and peace of mind is worth a little extra, so I would go with 840 Pro which still uses MLC. If you search slickdeals for the best deal 256GB 840Pro goes for as low as $210 on sale.
I recently posted about some performance issues I was having with SQL. I did give up on SQL, though I created an in-memory filter using a cache created as a hashset of a few merged SQL tables. For all cases I've tested, it works in real-time. The hashset is updated every 8 hours (taking about 4 seconds each update) and only takes up about 20MB of RAM.