Final Words

TRIM is a huge step forward in SSD maturity and readiness for the masses. There are only so many people who have the patience to listen to a NAND flash explanation to understand why their luxury storage device gets slower the more you use it. TRIM not only simplifies the problem but it makes SSDs work the way they should. When you delete a file TRIM ensures that the file is no longer tracked by the SSD. And it just works.

The driver limitations are a bit annoying, especially given Intel knew this was coming. Difficulty in coordinating schedules is one of the downsides of having such a huge organization.

It's also ridiculous that Intel has done nothing to take care of it's original X25-M G1 customers. Those who spent over $600 on Intel's first SSD deserve to be taken care of but instead they get no TRIM support and no SSD Optimizer. Both of these are things that Indilinx has offered it's customers before Intel. Vertex owners have had a wiper tool since before Intel ever announced intentions to enable TRIM on the G2.

The write speed improvement that the Intel firmware brings to 160GB drives is nice but ultimately highlights a bigger issue: Intel's write speed is unacceptable in today's market. Back when Indilinx first arrived there was no real threat, but today Intel is facing a much more mature group of competitors. Our heavy trace benchmark is a prime example of why this is an issue. I fully expect Intel to address it with the third gen drive next year but it makes buying a drive today unnecessarily complicated.

From a compatibility standpoint, Intel has the advantage. It's just a much larger company than Indilinx and has the ability to do more compatibility/reliability testing.

The performance side is a bit more difficult to break down. The more sequential writing you do to your drive the more you'll stand to benefit from Indilinx's higher write speeds. In nearly all other situations the two controllers perform similarly or Intel is in the lead. The fact that both controllers support TRIM makes it even more difficult.

The easiest way to decide continues to be to buy the largest drive you can afford. 64GB? Indilinx. 80GB? Intel? 128GB? Indilinx and 160GB Intel. If you're buying an Indilinx drive the rate of firmware releases pretty much dictates that you'll want to buy from OCZ or SuperTalent. None of the other Indilinx manufacturers have Windows 7 TRIM support yet (Crucial has now posted a firmware update with TRIM support). The additional testing and exclusive agreements that OCZ/ST have with Indilinx provide their customers a tangible advantage in this case.

Kingston's 40GB option is super interesting. Anyone who's sold on SSDs will probably opt for a bigger drive but if you're on the fence, the Kingston solution might be for you. The write speed is disappointing but for application launches and boot time it's got the speed. If Newegg can keep these things in stock at $85 after rebate it's a gold deal. I'd prefer the price without the rebate but these things are still selling at a premium unfortunately.

Next year SSDs will get even more interesting. I attended a couple of Intel's SSD tracks at IDF this year and got a glimpse into what Intel is working on. Through TRIM and other architectural enhancements Intel is expecting to deliver much higher consistent performance on its future SSDs, regardless of how full they are. We can also expect to see a decoupling of capacity from the number of channels the controller supports; right now Intel has a couple of oddball sizes compared to the competition, but future designs will allow Intel to more closely mimic HDD capacities regardless of controller configuration.

I still firmly believe that an SSD is the single best performance improvement you can buy for your system today. Would I recommend waiting until next year to buy? This is one of the rare cases where I'd have to answer no. I made the switch last year and I wouldn't go back, it really does change the way your PC behaves.

Introducing the AnandTech Storage Bench - Real World Performance Testing
Comments Locked

162 Comments

View All Comments

  • mbreitba - Tuesday, October 27, 2009 - link

    Looks like a lot of people are having problems with it, and Intel has pulled it :

    http://communities.intel.com/thread/7693?start=45&...">http://communities.intel.com/thread/7693?start=45&...

  • Griswold - Wednesday, October 28, 2009 - link

    If you actually look at the number of people with the issue and filter out the chit-chat, its not "alot" actually. However, my flash went just fine.

    Thats the risk with flashing firmware regardless of what device it is. Theres always the chance to brick it. Thats also why I dont understand why some people flash every fucking piece of hardware whenever theres a new firmware available - ok, this is a different case, here it makes perfectly sense.
  • strikeback03 - Wednesday, October 28, 2009 - link

    Has anyone had problems flashing a drive before they put any data on it? I have a new G2 still in the box that I just haven't yet had time to do anything with, was planning on flashing it then loading Win7 and Ubuntu 9.10 this weekend, have there been any reports of issues when loading an OS after flashing?
  • UltraWide - Tuesday, October 27, 2009 - link

    Great article, I like the definite conclusions and recommendations. Keep up the good work!
  • nicolasv - Tuesday, October 27, 2009 - link

    Hi Anand

    In 'The SSD Relapse' you state that the G2 "doesn't drop in performance when used...at all." Yet in 'The SSD Improv' the 80GB G2 with TRIM firmware drops more than 60% in the 4KB random write test.

    Granted, the charts and figures used in 'Relapse' to back its claim are for the 160GB G2 and these results are for the 80GB G2. What do you attribute this difference in performance to, the new TRIM firmware?

    As a Mac OS X user, at this point, I feel like I can only really consider drives that perform well without TRIM, especially in the <= 80GB range, so would appreciate your feedback.

    Cheers
    Nicolas
  • 7Enigma - Tuesday, October 27, 2009 - link

    I believe it is because in that particular test he is writing to the ENTIRE 80gig drive, so it's not that TRIM isn't working per se, rather that there is no free space to allow TRIM to do anything at all.
  • 7Enigma - Tuesday, October 27, 2009 - link

    As an addendum to my previous post, you can see that after file deletion the performance goes back to virtually new. So in a sense the performance of the drive never goes down, UNLESS you simply delete a partition rather than erasing the data on that partition FIRST and then deleting it.

    I think that's probably something that needs to be implemented with an updated driver, or at least a warning box that comes up saying "deleting this partition without formatting will hinder performance".
  • GullLars - Tuesday, October 27, 2009 - link

    I don't know if you have done extensive benchmarking with SSDs, but using IO QD = 3 for 4KB random in IOmeter don't yield representative results for intels SSDs. I have been benchmarking SSDs with some other guys for over a year now, and we have found that while Samsung and Indilinx scale from QD 1-4 and then flat out, Intels x25-M scales well all the way to around QD 10-16, and actually is capable of over 140 MB/s at 4KB random read at QD=64 in fresh state, and still over double your messured 60-64 MB/s in used state.

    In our benchmark thread, the records with x25-M from ICH10R before TRIM firmware are:
    IOmeter
    4KB random read QD=64: 40913 IOPS = 163,5 MB/s
    4KB random write QD=64: 19360 IOPS = 77 MB/s
    PCmark vantage HDD score: 43107.

    The same guy that got the random read and PCmark scores above also got PCmark vantage HDD score 120374 with 3 x25-M gen1 from ICH10R.

    In other words, the results posted for x25-M in this review are either in "used state" or below par.
  • Voo - Tuesday, October 27, 2009 - link

    You know Anand trys to simulate REAL situations and a QD of 10-16 is absolutly unrealistic for a home user - don't even talk about a QD of 64. Maybe the Intel SSDs shine there, but it's just of no interest.
  • GullLars - Tuesday, October 27, 2009 - link

    In his traced "light" benchmark with mostly single-tasking the average queue depth is 6.09. If you take into account that most of the sequential read and write operations (although they are under 30%) don't generate a queue, and that 4-16KB IOs often come in bursts with more queue depth, you can easily get a QD of more than 10 with relatively mild multitasking if it involves disk access. A harddisk's cache is regulary used as a buffer for the write portion of these, but if the cache is full your system almost freezes because of the harddisks low IOPS. An example would be if you try installing windows updates or a program while running a virus scan and listening to music or extracting a compressed archive, you will quickly notice if you try this on a harddisk.

Log in

Don't have an account? Sign up now