I've noticed my Macbook air (2nd Gen; 120GB SSD) slow down a fair amount since I first bought it (have not run benchmarks). Is there a wiper utility I could safely use from bootcamp? (I mount my Mac HD in the Windows OS using MacDrive).
Promising to hear there may be TRIM support implemented for 10.6
I'd like to state for the record, I'm constantly thinking about TRIM.
It is not bad or very bad. Security > lifespan of SSD, nothing is an excuse when it comes to the security of your data. Even secure trash once a day won't bring your SSD to death for another 2-5 years. It'll be fine.
As stated earlier, TRIM is in the ATA spec and is something on hardwarelevel. It's between the ssd and the controller. Filesystems have nothing to do with it, aka it's filesystem independent. However, it does have everything to do with the OS because the OS needs to have TRIM support which Win7 and Linux do (it seems that OS X also has something like TRIM support). Just make sure that whatever you use as a filesystem can be used in Windows 7/Linux or else it won't trigger TRIM.another question, does trim of win7 supports all kinds of file system or only the NTFS?
thanks!
As stated earlier, TRIM is in the ATA spec and is something on hardwarelevel. It's between the ssd and the controller. Filesystems have nothing to do with it, aka it's filesystem independent. However, it does have everything to do with the OS because the OS needs to have TRIM support which Win7 and Linux do (it seems that OS X also has something like TRIM support). Just make sure that whatever you use as a filesystem can be used in Windows 7/Linux or else it won't trigger TRIM.
In other words: as long as you have Win7 and an SSD that support TRIM it'll do TRIM regardless of whatever filesystem you put on it just as long as Windows can use it (that means NTFS and FAT32).
@ Davidkoh: why do you need TRIM that much? SSD's have a nice feature called garbage collection and the Indilinx drives will get an even better version of that garbage collection (it's a lot faster) combined with TRIM (the OS triggers TRIM, TRIM should trigger the garbage collection and make sure both do its magic). I don't think it will be a big problem if Snow Leopard does not support TRIM after all, the garbage collection will be enough. You can use SSD just fine, even at this moment without any TRIM support (because that's where we stand right now: there is no TRIM, only garbage collection). If you take a look at the Indilinx Barefoot drives you'll see they have enormous amounts of problems when using TRIM. There are some problems triggering TRIM at the moment you hibernate the machine, this will create dataloss. Other SSD's manufacturers also have problems with the TRIM implementation. TRIM is not really a good option right now, it is far too buggy and will cause dataloss so using TRIM would be a set back in technological progress.
Ok. I've been ogling SSD's for a while now. I was all set on the Corsair 256 until I read the Anandtech article. TRIM appears to be a major deal, performance wise. Will somebody please just tell me what to buy? The fan noise from running a 7.2k WD on my 06 MBP is sending me mental. Performance isn't a big issue for me, but I don't want to waste money by buying based on "new" specs that degrade overnight.
Will somebody be kind enough to make the decision for me? 160gb is adequate.
Thank you all.
Ok. I've been ogling SSD's for a while now. I was all set on the Corsair 256 until I read the Anandtech article. TRIM appears to be a major deal, performance wise. Will somebody please just tell me what to buy? The fan noise from running a 7.2k WD on my 06 MBP is sending me mental. Performance isn't a big issue for me, but I don't want to waste money by buying based on "new" specs that degrade overnight.
Will somebody be kind enough to make the decision for me? 160gb is adequate.
Thank you all.
You might want to do some more research and read very carefully what you are typing as you've already proved you're wrong about TRIM having to do with the filesystemTRIM does use the filesystem indirectly. It uses the filesystem to know which blocks contains deleted information. Every time you delete something what you essentially do is delete the "map" to that file from the filesystem. The OS will then send a TRIM command to the drive. The TRIM function keeps track of which blocks are empty (no data in) and deleted (data no longer needed) and different implementations will then take different actions.
It was a bug in the TRIM implementation by Indilinx and they have fixed that bug by rewriting the entire firmware. TRIM got triggered at the wrong time when hibernating causing dataloss which is exactly what I explained in my post. Seemed clear to me that this would refer to a bug in the implementation and not a bug in TRIM itself.Indilinx problems with dataloss have nothing to do with TRIM as a function in itself, it is a product of poorly written firmware by Indilinx. Good to note is that Indilinx seem to have have next to no internal testing, they seem to send it out to manufacturers using their controller and in some cases these let the customers test the firmware for bugs.