Saturday, August 18, 2012

Technical summary of real-world perfomance between SSD controllers and manufacturers.


Reliability, performance and usable space.

While looking for SSD promotions, stumbled across the SSD 60GB Benchmarks and Review on tomshardware.com. Have summarized about 3 hours of research and reading in this post with links to relevant sites.

"Using reliability as a differentiator ...we shouldn't be looking for the cheapest SSD, but rather the most trustworthy one."

"When it comes to picking a 60 GB SandForce-based boot drive, NAND type is the biggest determinant of performance"

"Samsung uses Toggle NAND in the 830, which is a little better than synchronous, and a lot better than asynchronous"


Right. So many brands, so many mixes of controllers and NAND types. Different sizes. Different manufacturer published benchmarks, different opinions in forums/blogs. And then there is the price difference between products from the same manufacturer. And price differences between manufacturers using the same controller type... Pretty confusing isn't it?

After playing the the OCZ synapse (please stay away from theses. It works, yes, but it affects reliability), the Intel 25M-G2, Intel 320, Crucial M4, Samsung 470, Samsung 830 over a period of two years.

Personally, my preference right now is the Samsung 830. Have actually SEEN it go to 400MB/s speed while doing a VMware Workstation VMDK defrag. The Crucial M4 comes at a close second with the max seen rate at around 380MB/s.

Samsung SSDs (mostly 470s) are used in MACs, HPs, Lenovos as their base HDD - this should be a great indicator of the reliability of Samsung's products.

In my humble opinion, when considering which SSD to buy, the type of NAND used and the controller within the SDD is the most important factors to consider. Before purchasing, research what kind of NAND is in use on the SSD. Avoid asynchronous NAND - it has a pretty bad performance penalty as the drive fills up. Also avoid those SSDs that use compression. I don't have a good impression of OCZ and there's a saying going around in forums for OCZ "Live fast die fast".

Lastly, from what I've read so far, it's generally not a good idea to use sector-level encryption for SSDs. It will hasten the wear out of the NANDs. My guess is that the OEM version of the Samsung 470 may have this consideration built into the design but have no way to confirm as yet.









What follows is a summary of the information from that article and some research on the 3(?!) types of NAND available in the SSD market now.

SUMMARY FOLLOWS:

SSD CONTROLLERS

Tests repeated on the SF-22xx-based SSDs accessing asynchronous NAND, found that only the 60GB capacities are affected significantly due to the low number of NANDS available for use by the firmware.

Read speeds are significantly impacted by the drive's free space. There is a noticeable drop-off on the lower-capacity SF-22xx-based SSDs due to compression and SandForce's foreground garbage collection mechanism.

Reading back information written on 60 GB Agility 3 falls between 150-200 MB/s and 450 MB/s on free space.

Intel 520 SSDs perform better, incompressible data is read back at 250 MB/s, 100 MB/s faster than the OCZ Vertex 3.

Crucial M4 (on Marvel controllers) use background garbage collection and does not compress data making it unaffected by the SSD's fill state.

FLASH MEMORY (NAND) TYPE


The OCZ Vertex 3 behaves alot like Corsairs' Force GT when it comes to the performance data using synchronous NAND.

It doesn't matter much which firmware on the various manufacturers, and how they are tweaked, as the SF firmware elements remaing the same. "The relationship between hardware and firmware (and how it affects features like TRIM and garbage collection) functions identically from one drive to the next" - be it on a MAC or a PC.

POWER COMPONENTS

There a cheap types which might fail earlier due to wear and tear (conjecture at this point)

OTHER OPINIONS AND COMMENTS FROM FORUMS







Thursday, August 16, 2012

Windows 2003 - Enable OS firewall to allow exceptions by IP(s) and IP range(s).

There is no elegant way to do this on Windows 2003 Server.

The following will add TCP ports 5500 to 5700 one at a time - run at the command line.

"FOR /L %I IN (5500,1,5700) DO netsh firewall add portopening TCP %I "Passive FTP"%I"

The inelegant way is to add port range, you can use the GUI to add that range to a defined port then export that registry entry and make changes to that .reg file and import it back.

Will update details at later time.