Setup
SetupStorage drive | Crucial CT64M225 SSD | Corsair X128 SSD | Samsung HD103UJ HDD |
---|---|---|---|
Drive capacity | 64GB | 128GB | 1,000GB |
Approx. price at time of writing | £115 | £290 | £55 |
Approx price per GB | 1.797 |
2.265 |
0.055 |
CPU | Intel Core 2 Duo E6700 (2.67GHz) | ||
Motherboard | Foxconn P45 Digital Life | ||
BIOS revision | P03 | ||
Memory | 4GB Corsair DDR2-1,066 | ||
Host hard drive | Seagate Barracuda 7200.11 500GB | ||
Graphics Card | Sapphire Radeon HD 4870 512MB | ||
Mainboard software | Intel
9.1.1.1015 |
||
Graphics driver | Catalyst 9.7 | ||
PSU | Corsair HX1000 | ||
Operating System | Windows 7 RC, 64-bit |
Tests
2D benchmarks | CrystalDiskMark 2.2.0m 6.15GB large-file read and write test 123MB small-file read and write test SSD-to-SSD transfer test Disk torture - writing 25,868 (3.72GB) files back onto drive |
---|
Setup notes
To give some idea of basic performance, we're comparing the Crucial CT64M225 against another Indilinx-powered drive in the form of the Corsair X128 128GB. We've also thrown in a 1TB mechanical HDD from SamsungCrystalDiskMark provides throughput data based on sequential reads and writes, and random (512K/4K) reads and writes. We've used the default 100MB file-size for the tests.
In terms of real-world benchmarks, we time how long it take to transfer two sets of files to and from a Seagate 7200.11 500GB drive equipped with Windows 7 RC. The large-file tests include two movies that total 6.15GB. The small-file test is the expanded CINEBENCH R10 benchmark folder that's 123MB in size but has 1,971 files, ranging from 26.5MB down to 1,600 or so files that are 4KB, or smaller. We appreciate that the host drive may prove to be a bottleneck in this case, yet it does represent a real-world scenario. Practically eliminating this, we've run an SSD-to-SSD test, to see how they perform in a best-case scenario.
Lastly, we timed how long it took to copy a folder containing 25,868 files (3.72GB) from the drive back to the drive, as a 'copy' folder. This test stresses the read, write, and controller efficiency.
Again, reiterating the comments on the first page, this is a brief first-look at performance.