There are some performance considerations when using full disk encryption on an SSD. Here's an excerpt that explains the underlying issue nicely:
You write in pages (4KB) but you can only erase in blocks (128 pages
or 512KB); thus SSDs don't erase data when you delete it, only when
they run out of space to write internally. When that time comes, you
run into a nasty situation called the read-modify-write. Here, even to
just write 4KB, the controller must read an entire block (512KB),
update the single page, and write the entire block back out. Instead
of writing 4KB, the controller has to actually write 512KB - a much
As discussed at great length in this masterpiece on SSD performance, SSD performance drops over time as the disk fills up. As explained above. Typically, when setting up full disk encryption, the entire disk is filled with random data so as to obscure the encrypted data from the free space. This, as I understand it (and I'm certainly no expert) means that using full disk encryption one immediately goes to the worst case performance of the drive.
So, understand that the performance hit of encryption on an SSD will be far more potent than on a regular spinning drive.
Second, because of the way data is read / written, again as above, the standard methods for securely deleting files (like the shred utility) don't apply to SSDs. If you're using full disk encryption from the beginning, no problem. But if you already have unencrypted data on the drive, you need to be careful to ensure you fully zero the drive first. I'm not sure how that is done, but I think it's discussed in the masterpiece.
Fundamentally, SSDs function in a totally different way to traditional spinning disks. The bulk of encryption software, secure deletion tools, and guidelines, assume that disks are made of spinning platters. That doesn't apply to the world of SSDs.
My advice to somebody starting out with full disk encryption on an SSD would be two-fold.
First, either start with a clean drive, or carefully zero it before you begin.
Second, under partition the drive. So partition 80%, or as little of the drive as you can get away with. The additional free space can help to maintain drive performance. It does depend on the specific drive, so you could research the details for the exact drive you have and so on, but as a general principle, it can dramatically extend the life of the drive.
Thirdly, and I realise I said two-fold, understand that full disk encryption will simply massacre SSD performance. Personally, that's a trade off I'm willing to make for the security that full disk encryption affords me, but there are alternatives, such as an encrypted home directory in Ubuntu. That type of encryption will likely perform much better on an SSD, although it does have other issues worth considering.