The Trim Command: Coming Soon to a Drive Near You

We run into these problems primarily because the drive doesn’t know when a file is deleted, only when one is overwritten. Thus we lose performance when we go to write a new file at the expense of maintaining lightning quick deletion speeds. The latter doesn’t really matter though, now does it?

There’s a command you may have heard of called TRIM. The command would require proper OS and drive support, but with it you could effectively let the OS tell the SSD to wipe invalid pages before they are overwritten.

The process works like this:

First, a TRIM-supporting OS (e.g. Windows 7 will support TRIM at some point) queries the hard drive for its rotational speed. If the drive responds by saying 0, the OS knows it’s a SSD and turns off features like defrag. It also enables the use of the TRIM command.

When you delete a file, the OS sends a trim command for the LBAs covered by the file to the SSD controller. The controller will then copy the block to cache, wipe the deleted pages, and write the new block with freshly cleaned pages to the drive.

Now when you go to write a file to that block you’ve got empty pages to write to and your write performance will be closer to what it should be.

In our example from earlier, here’s what would happen if our OS and drive supported TRIM:

Our user saves his 4KB text file, which gets put in a new page on a fresh drive. No differences here.

Next was a 8KB JPEG. Two pages allocated; again, no differences.

The third step was deleting the original 4KB text file. Since our drive now supports TRIM, when this deletion request comes down the drive will actually read the entire block, remove the first LBA and write the new block back to the flash:


The TRIM command forces the block to be cleaned before our final write. There's additional overhead but it happens after a delete and not during a critical write.

Our drive is now at 40% capacity, just like the OS thinks it is. When our user goes to save his 12KB JPEG, the write goes at full speed. Problem solved. Well, sorta.

While the TRIM command will alleviate the problem, it won’t eliminate it. The TRIM command can’t be invoked when you’re simply overwriting a file, for example when you save changes to a document. In those situations you’ll still have to pay the performance penalty.

Every controller manufacturer I’ve talked to intends on supporting TRIM whenever there’s an OS that takes advantage of it. The big unknown is whether or not current drives will be firmware-upgradeable to supporting TRIM as no manufacturer has a clear firmware upgrade strategy at this point.

I expect that whenever Windows 7 supports TRIM we’ll see a new generation of drives with support for the command. Whether or not existing drives will be upgraded remains to be seen, but I’d highly encourage it.

To the manufacturers making these drives: your customers buying them today at exorbitant prices deserve your utmost support. If it’s possible to enable TRIM on existing hardware, you owe it to them to offer the upgrade. Their gratitude would most likely be expressed by continuing to purchase SSDs and encouraging others to do so as well. Upset them, and you’ll simply be delaying the migration to solid state storage.

Free Space to the Rescue Restoring Your Drive to Peak Performance
Comments Locked

250 Comments

View All Comments

  • blackburried - Wednesday, March 25, 2009 - link

    It's referred to as "discard" in the kernel functions.

    It works very well w/ SSD's that support TRIM, like fusion-io's drives.
  • Iger - Wednesday, March 25, 2009 - link

    This is the best review I've read in a very long time.
    Thank you very much!
  • BailoutBenny - Tuesday, March 24, 2009 - link

    Great in depth article on flash based SSDs. I'm waiting for PRAM though.
  • orclordrh - Tuesday, March 24, 2009 - link

    Very illuminating article, very well written and researched. It made me glad that I didn't pull the trigger on an SSD for my I7 machine and regret not buying OCZ memory! I'm interested in adding an SSD as the scratch disk for Photoshop CS4 to use. I don't really launch applications very often, say once a week on the weekly reboot and keep 6-8 apps open at all times. I have 12GB of memory for that. The benchmarks were very interesting, but what sort of activity does Photoshop scratch usage create? Large files or random writes? What type of SSD would be most cost effective here?
    An SSD does sound better than a SSD!
  • semo - Wednesday, March 25, 2009 - link

    wait for ddr3 to enter the mainstream and buy loads of memory.

    use a ramdisk for your adobe scratch area. much faster than ssd and no wear to worry about (not that you would worry that much with modern ssds anyway).

    http://www.ghacks.net/2007/12/14/use-a-ramdisk-to-...">http://www.ghacks.net/2007/12/14/use-a-ramdisk-to-...

    there is also a paid for and more feature rich ramdisk out there. can't remember the name
  • strikeback03 - Wednesday, March 25, 2009 - link

    I'll have to check when I get home, but I believe the recommended size for the scratch disk is upwards of 10GB. So would need a motherboard that supports a LOT of RAM to give enough to main memory plus a scratch disk.
  • strikeback03 - Wednesday, March 25, 2009 - link

    I was wondering the same thing. I'd guess it would be a lot of writing/erasing, so an SSD might not be the best from a longevity standpoint, but if your system is hitting the scratch disk often then the speed might make it worthwhile.
  • mikepers - Tuesday, March 24, 2009 - link

    Anand,

    I wanted to compliment you on what I think was an excellent article. This is the type of thing I really have always liked from Anandtech. The detailed background, the technical reasons for the issues and then a thorough review of the current state of things.

    I just finished upgrading my desktop. The only remaining item I wanted to replace was the hard disk. I had been thinking about getting a Velociraptor but instead I just ordered a 60GB Vertex from Newegg.

    Thanks again for all the work.

    Mike P.
  • ameatypie - Monday, March 23, 2009 - link

    That sure was a lot to take in! Fantastic article though, it has really opened my eyes to the possibilities that Solid State Drives provide. Probably wont be buying one in the immediate future given the so-called depression and such things, but i will certainly keep up with SSD progress.
    Thanks again for your fantastic articles - im sure im not the only one who really appreciates them :)
  • coopchennick - Monday, March 23, 2009 - link

    Hey Anand, I just finished reading through this whole article and I'm very impressed with the thoroughness and how informative it was.

    You just acquired a new regular reader.

Log in

Don't have an account? Sign up now