aggieNick02
Joined 3 years ago
Joined 3 years ago
https://pcpartpicker.com/forums/topic/425127-benchmarking-op...
You can compare their benchmarks with the other almost 400 SSDs we've benchmarked. Most impressive is that three years later they are still the top random read QD1 performers, with no traditional flash SSD coming anywhere close:
https://pcpartpicker.com/products/internal-hard-drive/benchm...
They are amazing for how consistent and boring their performance is. Bit level access means no need for TRIM or garbage collection, performance doesn't degrade over time, latency is great, and random IO is not problematic.
That option is much better than getting the undo/redo vs unsaved changes tracking wrong and allowing unsaved changes to be easily lost, like notepad does. :-P
0) Set "When Notepad starts" option to "Start new session and discard unsaved changes"
1) New file
2) Type "abc" - note the "X" to close the file changes to a "O" (pretend that's a circle) to indicate unsaved changes
3) Save file - "O" changes back to "X"
4) Type "def" - "X" changes back to "O" because "def" is not on the file on disk
5) Undo, "def" disappears, "O" incorrectly remains...
6) Redo, "def" reappears, "O" incorrectly changes back to "X"
7) Close file. No prompt to save unsaved "def". Reopen file. "def" is gone
Most modern motherboards, on boot, will block "security operations" on a drive where the security password is set to the default (because it hasn't been manually set by the end-user). They do this to prevent malware from being able to set a password on a drive that hasn't had its password set. (Malware could set the password and I believe configure the drive to effectively brick it.)
But many (probably most) motherboards fail to correctly block "security operations" on a suspend/resume. This is bug 2, and makes suspend/resume often an effective workaround for a drive with bug 1, as well as a theoretical opportunity for malware to easily inflict damage on all drives that support "security operations".
So one generally ends up stuck and unable to securely erase their drive when it has bug 1 and is installed on a motherboard without bug 2. In this case, you have to hope your motherboard has a feature in its BIOS to, on next boot, not block security operations. Otherwise you're stuck and need to find another motherboard if you want to sanitize your drive, or hope that a firmware update for your drive resolves bug 1.
The full details are in this comment on a Github issue from 2016: https://github.com/linux-nvme/nvme-cli/issues/84#issuecommen... . It was one of the most rewarding bugs I've had the fortune to get to the bottom of. We were extra motivated to fully understand it when we moved to a new SSD benchmarking test system that turned out to not have bug 2: https://pcpartpicker.com/forums/topic/460000-an-ssd-that-can...
I had the fortune to be involved developing the LEGO Mindstorms EV3 programming software. Under the hood, it was a small web browser shell (using Mono on Mac and WPF on Windows) around a Silverlight Out-of-Browser app. Anything beyond the permissions of the Silverlight app (e.g. bluetooth/USB comms) was an RPC from Silverlight to the shell.
After completing the Mac/Windows app, LEGO wanted to deliver a similar experience on iPad. There was no Silverlight there, and it was clear there never would be. But we were able to leverage Xamarin stuff to reuse most of the same codebase, just with an iOS UI on top.
For example, I'll say: "OK Google, Play 'Hey Jude' by 'The Beatles'". Sometimes I'll get that song. But many others I'll get "Hey Jude" by a Beatles tribute band... I wouldn't be surprised if the version by the tribute band is cheaper to play.
Congrats on the launch and bravo on such a well-polished everything - product, UI, website, etc. Very impressive.
The quick conclusion? "Quick Wash" uses less energy and water than "Eco Wash". "Intensive Wash" uses more energy than both.