Latest News Posts

Latest Forum Posts

Western Digital SiliconEdge Blue 256GB

by Robert Tanner on April 19, 2010 in Storage

The SSD market is littered with competitors, but up to now, few companies behind mechanical storage have entered the arena. Last month though, Western Digital scratched its name off the list, with the help of its SiliconEdge Blue models. We’re taking a look at the 256GB variant here, so let’s see how it fares against the competition!

Real-World: File Transfers, Adobe Lightroom

File Transfers

For this test we took a 7.16GB Dual-layer DVD image and timed how long was required to transfer it to a different 10GB partition created on the same drive. Keep in mind with a hard disk, this requires the actuator arm to seek back and forth between the source and destination sectors of the disk platter, while any SSD can instantly read and write to multiple flash chips at once. Still, this is not a test of the raw write speeds of a SSD as the SSD controller cannot read & write to the same parts of the NAND flash simultaneously.

This is the moment of truth, where we double-check the unusual and surprising synthetic results in write performance. The Western Digital SiliconEdge Blue almost manages to finish the transfer before we can say the mouthful of a name aloud, and takes first place with an equally surprising one minute and twenty-two seconds. Perhaps there was something to those synthetic numbers after all.

Adobe Lightroom 2.5

For this test we utilize 500 large RAW files, and import them into Lightroom. We time how long it takes the program to import the files, cache them, and build the image library.

Somewhat interesting is that the results are split into two main groups with the Summit only able to tie the hard drive, while the other SSDs clump together around the 3 minute mark. It appears the Lightroom test is not demanding enough, and another system component (likely the CPU) has become the bottleneck here rather than the storage. Remember, Lightroom only utilizes two cores when loading and creating its image library, so it is not fully utilizing our quad-core CPU.

This should go to show that not all workloads are bottlenecked by storage, and that to get the most out of a fast SSD it will require an equally matched processor and system as to avoid any system (or in this case software) bottlenecks.