That's why I used HDDerase. It can restore intel drives to a pristine state in terms of performance. But it wipes everything and requires that you use version 3.3 since 4.0 doesn't support intel drives.
Here's the quote from intel, addressing the issue on G1 drives without Trim, which unfortunately is where OS X is at. (boot into a windows partition on another drive, and use the intel tool to wipe the disk also)
SSD devices are not aware of the files written within, but are rather only aware of the Logical Block Addresses (LBAs) which contain valid data. Once data is written to a Logical Block Address (LBA), the SSD must now treat that data as valid user content and never throw it away, even after the host deletes the associated file. Today, there is no ATA protocol available to tell the SSDs that the LBAs from deleted files are no longer valid data. This fact, coupled with highly random write testing, leaves the drive in an extremely fragmented state which is optimized to provide the best performance possible for that random workload. Unfortunately, this state will not immediately result in characteristic user performance in client benchmarks such as PCMark Vantage, etc. without significant usage (writing) in typical client applications allowing the drive to adapt (defragment) back to a typical client usage condition.
In order to reset the state of the drive to a known state that will quickly adapt to new workloads for best performance, the SSDs unused content needs to be defragmented. There are two methods which can accomplish this task.
One method is to use IOMeter to sequentially write content to the entire drive. This can be done by configuring IOMeter to perform a 1 second long sequential read test on the SSD drive with a blank NTFS partition installed on it. In this case, IOMeter will Prepare the drive for the read test by first filling all of the available space sequentially with an IOBW.tst file, before running the 1 second long read test. This is the most user-like method to accomplish the defragmentation process, as it fills all SSD LBAs with valid user data and causes the drive to quickly adapt for a typical client user workload.
An alternative method (faster) is to use a tool to perform a SECURE ERASE command on the drive. This command will release all of the user LBA locations internally in the drive and result in all of the NAND locations being reset to an erased state. This is equivalent to resetting the drive to the factory shipped condition, and will provide the optimum performance.
Intel provided the tool to SSD reviewers, in this case HDDerase 3.3 which is able to perform the secure erase command. It takes ~2ms per block of 512KB, and on the 80gb drive took like 20 seconds.
http://www.pcper.com/article.php?aid=669&type=expert&pid=6
I don't think that HDDerase runs straight on a mac because EFI doesn't support the necessary bios level commands, so I pop the drive into my dell mini and do the erase there... here's another macbook pro owner's experience.
http://www.markc.me.uk/MarkC/Blog/Entries/2009/8/13_Erasing_an_SSD.html
