MacBook – Why don’t I see a significant boost in performance moving to SSD on MacBook7,1

I disagree with Randolph's Answer. If anything, the article says exactly the opposite of the "good performance for a while" part.

What we found was the exact opposite: an OS that doesn't appear to be affected by SSD performance degradation

And I don't have Apple's SSD. I have an OWC on a Mac Pro and haven't had any performance degradation since I brought it, about six month ago. Before that, I had an Intel drive and also never had degradation problems under OSX. I changed the drive because my 1st drive was too small. That Intel-M drive is running on a laptop with Windows 7 Home Premium.

So far, it has been proven that OS X doesn't suffer from the lack of TRIM support; what we don't know if that's because the OS/FileSystem is doing something different or because there's TRIM support hidden and not reported.

In any case, getting a SSD is really a performance increase. I only use it for the OS and some minor things, the rest sits on a mirrored SATA RAID, but this is a Mac Pro, so things are different.

On small Macbooks, the usage of SSD is like day and night and I haven't seen performance degradation over the course of a Year.

Maybe there is one, but if that's the case, it's so slow that by the time is significant, you'll be either changing the drive or the whole computer.

I've been using SSD since late 2009.

I recommend you don't get one from Apple, as they tend to overcharge. Get one of the many SSD's alternatives like Corsairs, Intels or the OWC I have, which I heavily recommend.

But the SSD market is in a constant evolution, so read before you buy.

I have the same problem, which I'm pretty sure is due to a combination of the way write operations work on flash memory and the way core storage (or any whole-volume) encryption works.

First, write behavior: unlike volatile memory (the stuff used in the memory of your computer) or hard disks, where any bit can be written to 0 or 1 at any time, flash memory has two main states: written and erased. Within "written" are 0 and 1. When you need to write to flash memory you must write an entire block that is currently in the erased state. File system software in the OS may know what blocks are free, but the controller and storage on a flash device don't. A special way for the OS to tell an SSD to make blocks available has been devised for "bus-connected" SSDs: it's called TRIM. USB protocol stacks don't, to my knowledge, support TRIM. So, basically, flash memory continues to fill up until there are no actual erased blocks, at which point the file system has to erase and rewrite blocks by reading them, merging in the new data, erasing, and writing them back out. That's why you see small-file write performance degrade on SSDs over time.

The special circumstances of encrypted volumes is interesting: depending on the way the encryption works, it may actually encrypt an entire volume, filling all the blocks with what appears to be random data even if the blocks are actually unused and would contain zeroes. So when you turn on FileVault (or otherwise enable core storage encryption), it basically consumes the entire volume, leaving no space for write operations. The file system has to constantly read, erase and rewrite blocks so that it can rewrite them with any encrypted data you want to put on it.

Now I will say right here that this is speculation based on a reasonable understanding of how things work, but there are people who actually know the details, who may correct or improve my explanation and I hope that they will do so.