I've been running SSDs in my laptops for several years without issue. The big no-no with a solid-state drive is running your paging file on it. For those unfamiliar, the page or paging file is a chunk of your hard disk (be it solid-state or rotating) that the operating system uses as fast-access RAM rather than for storage (the filename in Windows was "PAGEFILE.SYS" forever; it probably still is). SSDs have a limited, but undefined, number of write/rewrite operations for each location "on the disk" so to speak. As the operation count racks up, the drive will eventually get slower and more unreliable.
Anyhow, since the page file is used as RAM, the operating system is continuously reading, writing, and rewriting to the drive. The page file is dynamic: If you have it set to 50MB it will
always use 50MB of drive space, but it doesn't use the same physical location of those 50MB. It writes in whichever location is most quickly accessed, so that 50MB can be spread out anywhere in the drive. That wears out the
entire SSD much more quickly, rather than just beating the same 50MB of drive into oblivion. It does not care about partitions, either--it's going to use space wherever it wants. Partitions are not a physical location boundary in the disk, they're simply a digital allocation of space. Think of a partition as a law defining a country's border. The words on the paper have no idea where the physical location of said border is, they're just a bunch of ink that defines its location. A partition is just a group of digital 1s and 0s that define how much space is consumed a drive partition.
The recommendation for SSDs in a single physical drive application like a laptop is to
completely disable the page file. That kind of sucks, because SSD page files are truly fast--for a short period of time. Instead, you should bulk up on RAM--max it out, in fact. In multiple-drive applications, the page file should be on a spinning disk, which has a much-longer lifespan in terms of writes/rewrites (the higher RPM the better, from a performance standpoint).
SSDs shouldn't be defragmented, either. It's pointless, since it does not speed the drive up a'tall--you're not moving data from far-flung reaches of spinning media, so there's no performance improvement. In fact, it's detrimental since defragging simply raises the write/rewrite count on every bit it handles--ultimately
slowing down the drive long-term.
I replace my SSD after three years
*, when the performance has diminshed to the point where my laptop seems like it's got a standard physical disk drive in it. The old drive gets wiped and stockpiled, since there's no bringing them back to their original performance level of which I'm aware. I have two old ones now: one is a backup of my current "working" drive and the other is disconnected but filled with "archive" material: important photos, tech info, videos, and music files that I absolutely do not want to lose. Each time I replace I go to a larger drive so that I can archive more to a known-good (if no longer fast) drive. I'm currently on a 250GB drive; prices have dropped below the "century mark" for 1TB SSDs, so the next one will be that large. I don't need one that big on this machine, but when the time comes it'll make a nice archive drive.
If Bullitt Beanie (
@dodgechargerfan) has contradictory or additional advice on this, listen to him rather than me. This sort of thing is his living; my finger ain't on the pulse like it once was.
* I have not yet replaced the SSD in my Toughbook. After 5 years, that PC still only has about two hours' use on it (setup time only) and hasn't been on since. That's my "EFI only" PC, which is why it's a Toughbook: If I get frustrated and throw it, it will survive. 