There are other threads about this. You can use it for a r/w intensive app to keep the r/w's away from your ssd. It is useful for resident cache directory and files. Pagefile.sys can go on one.
It
can, but...
Putting pagefile into a ramdisk is pointless unless I'm missing something obscure. You only need pagefile if you run out of ram. So leave your extra 8gb of ram free and you won't need the pagefile at all. That's what I do.
Actually, you are missing things, but they're all more reasons not to do it .
A PF on your non-volatile storage device provides,
at least, the following features, even if you aren't out of RAM:
1. If on the OS volume, minidumps. If you get repeated BSODs, but have no PF, turn the PF back on for the dumps.
2. A backing cache. Basically, write stuff in RAM, that's not getting accessed, to disk, preemptively, so that when you need more RAM, the pages that haven't been used much can be evicted, without the added wait time of pushing other data to the PF on-demand (just free up space that is known to already be in the PF).
3. Overcommit padding. Applications request X amount of RAM. They might not use it all, but they expect the OS to be able to provide it, if needed. The OS assumes they won't use it all, too, so allows more memory to be committed than it thinks will be used--but, it's not always right. The page file counts as additional available memory, so the OS can commit more than it has RAM, by treating the PF as added system memory.
Your PF should be on a disk drive, or non-existent (but, if
this series is too much reading, then just
leave it alone). Putting it in a RAM disk only serves to waste resources.
You can def use it for games.
Especially any game where there are lots of loading times as you move between areas (games like dragon age, skyrim, etc). Load the whole sucker onto a ramdisk and you're looking at probably a factor of 10 decrease in load times.
On one hand, sure. On the other, 120GB SSD would be more versatile, given the cost.