Nintendork :
For browsing just put your cache on an HDD or ramdisk
You know, it's funny. When I first started using SSDs, I'd put the OS on them and not much else. Then, as more information came to light about their reliability, I decided to use larger drives & overprovisioning (which I've had mixed success with, recently) to give myself a bit more confidence.
As Paul Alcorn has stated (I don't know if it's in any articles on this site, or just elsewhere + forum comments), that SSDs can write a lot more data in their lifetimes than HDDs. Given this point, the only argument
in favor of using HDDs instead, would be if you're trying to reduce the amount of data written by virtue of HDDs' slower speed. This might come into play, sometimes, but given the data rate of the writes concerning me, I think it wouldn't help.
In any case, I'd rather go for a quiet, power-efficient, non-mechanical solution. So, though overprovisioning and larger capacity drives, I'm all in for SSDs. The only exception is my media/backup server, which has a RAID 6 of mechanical disks. That's purely due to $/GB and because I don't need the speed of SSDs. It's not running, most of the time.
Nintendork :
for windows, disable prefetech. Move the page file to an HDD.
Prefetch doesn't hurt anything, because it's reading. As long as you have some RAM to spare, you'll do slightly better with prefetch
enabled.
I'd imagine the page file doesn't see a lot of use, unless you're running low on free RAM. It'd be interesting to see some actual data on this (does anyone know of a way?).