This is why you want TRIM

Kulith

Limp Gawd
Joined
Dec 13, 2009
Messages
259
This is my OCZ vertex after 6 months with no trim. I've been to the OCZ forums and apparently I've been using the wrong intel drivers this whole time because the intel drivers back form December didn't support trim, or some shit like that.

Anyways, now I have to do a firmware update and a sanitary erase and a windows 7 reinstall to get my performance back. Just thought you guys would like to know since lots of people are giving up trim in order to run raid...

2jac0ep.png


331dsuu.png
 
The new Intel driver was 9.0. version or something like that right?

the Trim supported intel drivers are Intel Rapid Storage v9.6 or newer

But if youve done a clean install recently the Microsoft drivers support trim as well.
 
The Vertex 1.5 on up firmware does excellent garbage collection when in RAID FYI. Personally, I don't have a need for TRIM. The GC is very robust on the latest Vertex's fw...
 
Well Indilinx isn't that fast to begin with, if we look at random I/O. Still a decent SSD though; not JMicron or Samsung. :)

The Vertex 2 has Sandforce controller and by default have 28% spare space. This would help a lot if running in RAID; by preventing erase block fragmentation. The erase blocks on non-Intel SSDs are also pretty big: 512K while Intel uses 128K erase blocks.

That means if you change 4 kilobytes, the SSD has to erase 512K and write 512K; just to effectively write that 4 kilobyte. Garbage collection is nice, but it does costs a lot of write cycles and thus lowers the lifetime of the product.

Ultimately, using the product in the best possible way would mean you benefit most from its advantages.
 
I use both Gen 2 intels and Vertexes all day everyday on W7, I honestly think the Vertexes feel faster in what I do. You can bench all day long and compare 4k writes all day long, but my own user experience is what matters to me.
 
Yes, but you should know subjective evaluations are very subject to the 'placebo' effect.

Generally, you need overall 30-40% performance improvement for a user to really notice outside of the placebo effect. Even with a cheap Indilinx SSD, you may already pushed the disk I/O bottleneck way below your other components (CPU/MEM).

If all you do is copy large files, then the difference between the two is minimal, and the Vertex also writes faster sequentially; so it could in fact be faster in this area. Whenever random access is concerned they are a lot faster though; and Intel has the lowest access times of any SSD; probably due to it not using the DRAM memory chip for write-back, and because of using 34nm NAND; the next generation 25nm will have even lower access times.

Access times are primarily important on blocking read I/O; actually quite common on Windows. So it could be considered the prime spec for an SSD. Still i think the difference between Access times and IOps is not very well understood by a large group of generally knowledgeable users.
 
As comparison: the Intel X25-V 40GB which only writes at 45MB/s does get 45MB/s random write and 200MB/s+ multiqueue random read. That's just with 5 channels, and i think that's very impressive.
 
Yeah, my own personal use doesn't really require constant, intensive IOPS for the most part, which is where the intels shine.
 
I use SSD's on linux boxes (I haven't installed a trim supporting kernel yet) and don't really notice slowdown in day to day use. My vertexes, agilities, etc are on 1.5 firmware. GC should be in effect.

No problems at all with speed...
 
Garbage collection is nice, but it does costs a lot of write cycles and thus lowers the lifetime of the product.

incorrect. it doesnt cost anymore write cycles than any other method. if the block needs erased and rewritten, it needs erased and re-written, no matter what method you use to do it. a dirty block needs cleaned, period. GC does not cause it to be cleaned "more" than any other method.
 
Last edited:
Isn't Trim or lack thereof something that affects writes only? It seems that something was going on with your reads also, which makes me wonder if your issue was something besides trim?
 
Isn't Trim or lack thereof something that affects writes only? It seems that something was going on with your reads also, which makes me wonder if your issue was something besides trim?

I think the 1.4 firmware in general had multiple problems.
 
Back
Top