Performance Limits And Pitfalls
Let’s cover a few things that must be considered when planning a transition to SSDs. We've already mentioned issues with sustained performance in prior SSD articles. This was an issue with older drive generations but has been improving over time. Still, you should take precautions. Most of the following items are valid for client PCs as well as for business and enterprise deployments.
Technically, all SATA drives can be utilized in RAID arrays using suitable controllers. However, some products don't deliver expected performance in RAID configurations. This is often a firmware issue, but should be checked nonetheless before investing in specific SSD products. Sometimes the TRIM feature (see below) won’t work on RAID configurations due to incomplete AHCI support.
Hard drives should be defragmented on a regular basis to make sure that frequently-used files are available on the faster sectors and that larger files aren’t unnecessarily scattered across the hard drive, which increases the time needed to retrieve them. Hard drives need to read and write sequentially as often as possible because head physical movements introduce latency. This isn't a problem for SSDs since data is always distributed by the SSD controller all over the drive. This is normal. Applying defragmentation tools to SSDs will be counter-productive, wearing down flash cells without introducing any advantage. Hence you should switch defrag off.
The TRIM feature is used by the operating system to inform the SSDs about blocks that were deleted and are available for new data. This allows SSDs to optimize writes in a way that maintains maximum write performance and optimizes wear leveling. SSDs do this internally, but the process is more efficient when triggered by the file-aware operating system. TRIM requires support in both the SSD’s firmware and the operating system. Drivers and the storage controller must support AHCI, as well. This often means using Windows 7 or Windows Server 2008 R2, Linux kernel 2.6.33, or FreeBSD 9. All older system versions will not support TRIM, which can result in severely limited write performance. However, TRIM support is complex, so double check that support is possible and enabled.
TRIM is supported by Intel SSDs with firmware 02HA and up, Indilinx 1819 and up, all JMicron 612 and 618 devices, Marvell hardware with firmware 0002, all SandForce devices, Samsung’s VBM19C1Q firmware for PB22 drives, and all Samsung 470 SSDs. The tool Crystal Disk Info provides great help with firmware and SSD checking.
Current page: Performance Limits And PitfallsPrev Page Business Metrics Next Page Recommendations For SSD Deployment
Stay on the Cutting Edge
Join the experts who read Tom's Hardware for the inside track on enthusiast PC tech news — and have for over 25 years. We'll send breaking news and in-depth reviews of CPUs, GPUs, AI, maker hardware and more straight to your inbox.
Very good article; times of most affordable capacity in SSD units is coming...Reply
A very good article. I love these articles explaining everything. I'm planning on buying two OCZ Vertex 2E 60GB for RAID-0 when I get enough money. Can't wait, should be one hell of an upgrade from a single 5400rpm WD green drive.Reply
Memristors might make SSD's sorter lived than people thought, but who knows. Great article btw.Reply
From what I understand, TRIM is supported under IDE mode using Win7 as well so you do not need AHCI. I have a Samsung’s VBM19C1Q firmware device and running IDE mode.Reply
Great article!! :DReply
Earlier this year we deployed a 5 node failover cluster with iSCSI backend. Each of the VM Host servers utilize a pair of solid state drives for booting and operating, with VM's running off of iSCSI shared cluster volumes. The servers are unbelievably fast and stable - 6 months of 100% uptime on Windows 2008R2. We only use magnetic HDD's now for transporting backups off site.Reply
One thing that I'm very curious, if we follow Tomshardware's advice to turn off disk defragmentation, the files on SSD would be defragmented over time.Reply
Upon SSD data loss, can we recover the data files if it's defragmented, especially on a SSD that has never been defragmented as Tomshardware had recommended?
Defragmentation of an SSD is not entirely unnecessary. It's important to distinguish between file fragmentation and free space fragmentation. The former is not an issue with SSDs because all parts of an SSD can be read at the same rate (the same is true for writing if the blocks are clean). But fragmentation of free space, whereby free space is largely distributed across partially-filled blocks, can severely reduce the performance of an SSD. Any time a file of <512kB is written to an SSD, it will take up only part of a block. However, the SSD will eventually run out of clean blocks and will need to re-arrange the data by erasing partially-filled blocks and consolidating them to free up more blocks for further writing. Running a free space defragmentation on the drive will aggressively consolidate the data on-demand so that you don't have the problem occurring when you didn't plan for it.Reply
Most SSDs will perform this process themselves when idle for extended periods, but it happens at a slow rate. This is what most manufacturers refer to when they talk about Garbage Collection.
Please send me the four fastest 256GB SSDs on the market, so that I might perform my own comparison ... I'll just sit by the door and wait for UPS to arrive.Reply
Thanks, in advance !!
= Alvin =
I put an SSD in my new computer and it was good but after i got the firmware update and changed to AHCI it was AMAZING (OZC Vertex 2 60gb). I would say tho that 60 gb is not enough, i installed windows photoshop and a few other design programs and i only have 20GB leftReply