I'm considering getting an SSD drive to run as the primary OS partition. As I understand, this should provide a substantial improvement in performance. My question is this: Should I leave the swap file on that drive? The swap partition will be largely random seeks and so should benefit from the speed. On the other hand, it will be constantly written to which will wear out the drive faster.
|
|
Source: Microsoft Guidelines (PDF, p.9) now, that is Microsoft's take on Windows with Solid State Disks, however, in a desktop PC, you might use a secondary platter hard drive as location for virtual memory. |
||||||||||||||
|
|
|
I have a better answer: Why, when you can just buy more RAM? RAM is as cheap or cheaper than SSD space. It's also much faster, and it will never (well, almost never) degrade like SSD drives do. Swapping memory to disk is a symptom of not enough RAM. If you need to speed up swapping, don't speed up the swap disk, upgrade your RAM and the swapping will go away. Swapping should be considered a last-resort backup plan anyway. |
||||
|
|
|
Please check out this article. http://www.storagesearch.com/ssdmyths-endurance.html 51 Years!!! I don't think I deserved all the down votes, but I guess you can always vote this down Best regards. |
||||||
|
|
|
I would be inclined to say that the performance gain from it is not worth it, especially if you have a lot of RAM. If you have at least 2GB RAM, you probably won't page a ton anyway so the benefits would be minimal. Not to mention that SSD sizes are relatively small, so you may not want to eat up a few GB worth of pagefile on it anyway. |
||
|
|
|
|
I think it would depend on how much RAM you have and how your "swappiness" is set. I have a swap set up on my computers, but if I don't hibernate, I rarely write to it. I tend to not max out my RAM usage. But if you know you're hitting swap a lot, I'd say no. If you don't hit it a lot, I'd say go for it. |
||||||
|
|
|
Patrick Regan's answer about "swappiness" is pretty spot on: depending on your usage, it might be fine, and if you're using Linux you can tweak "vm.swappiness" in sysctl (as described in an earlier question) for your use. So I'm tempted to say yes, as long as you give lots of disk to your swap. I've been hearing lots about the internal controllers on SSDs having super-tweaked algorithms to combat write wear, so in theory this would help -- give it lots of space, and set the kernel swappiness level low, and the SSD controller can spread the writes out and prevent any wear trouble. So that got me to wondering what the largest swap partition could be. I locked onto your mention of "swap partition" and thought "linux", so I looked into the maximums there. Turns out you can create ridiculous things like 16TB swap partitions, at least based on the kernel math. mkswap might not be able to actually initialize that partition, but the kernel supports it. However, the kernel can't use it. According to this, 16GB is about the biggest swap partition you can make and use in a modern linux kernel. So yes, you can, if your usage is going to be fairly swap-free. If you'll be swap-heavy, though, maybe a cheapo USB key for ReadyBoost (or the Unix equivalent) would be a better fit -- that way when your swapping destroys the device from overwriting, it'll be cheap to replace and won't cost you the price of another SSD. |
||||||
|
|
|
Unless you need the swap file (for suspend to disk for example), I would simply turn swapping off and get rid of your swap partition. The point of swap is to provide an extra cache level. Since your SSD has a low latency, the gains of using swap are much lower. If your system hardly ever swaps, then it makes even more sense to just get rid of it. I've been running a few linux boxes without any swap for a few years now (on regular HDDs) without performance issues. Any box with > 2GB of RAM I just don't bother with swap. |
||
|
|
|
|
http://www.storagesearch.com/ssd-buyers-guide.html This should provide accurate info. |
||
|
|
|
|
A solid state device has no moving parts, so wear is not an issue as it is with older devices. |
||||||||||
|
