Our testing methods
We have a full suite of performance results for literally dozens of different SSDs, but today, we've narrowed the field to include only the highest-capacity models available in the Benchmarking Sweatshop. Most of these drives offer 240-300GB of capacity, so they have much less storage than the Vertex 4 512GB. However, the higher-capacity flavors of those other drives don't carry substantially higher performance ratings than the models we've tested. In most cases, the performance specifications are identical, so we should have a good look at how each family of drives performs in its optimal configuration.

We've included a Western Digital Caviar Black mechanical desktop drive for reference, which gives us more than enough fodder for overstuffed graphs. Our test methods and systems haven't changed, so the Vertex 4's scores can be compared to those in any of our storage reviews dating back to last September.

If you're familiar with our test methods and hardware, the rest of this page is filled with nerdy details you already know; feel free to skip ahead to the benchmark results. For the rest of you, we've summarized the essential characteristics of all the drives we've tested in the table below. Our collection of SSDs includes representatives based on the most popular SSD configurations on the market right now.

We used the following system configuration for testing:

Thanks to Asus for providing the systems' motherboards and graphics cards, Intel for the CPUs, Corsair for the memory and PSUs, Thermaltake for the CPU coolers, and Western Digital for the Caviar Black 1TB system drives.

We used the following versions of our test applications:

• Intel IOMeter 1.1.0 RC1
• HD Tune 4.61
• TR DriveBench 1.0
• TR DriveBench 2.0
• TR FileBench 0.2
• Qt SDK 2010.05
• MiniGW GCC 4.4.0
• Duke Nukem Forever
• Portal 2

Some further notes on our test methods:

• To ensure consistent and repeatable results, the SSDs were secure-erased before almost every component of our test suite. Some of our tests then put the SSDs into a used state before the workload begins, which better exposes each drive's long-term performance characteristics. In other tests, like DriveBench and FileBench, we induce a used state before testing. In all cases, the SSDs were in the same state before each test, ensuring an even playing field. The performance of mechanical hard drives is much more consistent between factory fresh and used states, so we skipped wiping the HDDs before each test—mechanical drives take forever to secure erase.

• We run all our tests at least three times and report the median of the results. We've found IOMeter performance can fall off with SSDs after the first couple of runs, so we use five runs for solid-state drives and throw out the first two.

• Steps have been taken to ensure that Sandy Bridge's power-saving features don't taint any of our results. All of the CPU's low-power states have been disabled, effectively pegging the 2500K at 3.3GHz. Transitioning in and out of different power states can affect the performance of storage benchmarks, especially when dealing with short burst transfers.

The test systems' Windows desktop was set at 1280x1024 in 32-bit color at a 75Hz screen refresh rate. Most of the tests and methods we employed are publicly available and reproducible. If you have questions about our methods, hit our forums to talk with us about them.