Is a page file used all the time when you have 8 GB of ram?
Virtual memory is. You have no control when a page is committed to disk, that's up to the OS. IIRC, older 'stale' pages are normally committed to disk after a while, regardless of how much RAM you have.
If the people at Corsair recommend not putting those files on my SSD, I'm going to take their advice to heart. To each their own, as the saying goes.
As you said, to each their own: I know some people will short-stroke their hard disks to get absolute maximum performance in exchange of huge amounts of wasted hard disk space, and I personally would never do that as it does not suit *my* needs.
What I am giving you, however, are facts: each drive in my SSD array has over 19,000 power on hours. Forgetting for a moment it is a three drive RAID 0 array, let's pretend it's a single 240 GB SSD. In that case, in over 2 years of 24/24 usage, *with* the page file and temp files in the SSD, the drive had 15 TB written to it (5 TB per drive * 3 drives). Since the Media Wearout indicator is a function of the number of bytes written vs. total space available on the drive, for a single 240 GB SSD this indicator would remain at 97% (same as the number in each of the drives).
Now do the math. How long do you think this drive will last at the current usage levels?
What I am trying to point out is that some things are just not worth doing, if done for the wrong reasons. If you are transferring your page file to a hard drive because you are under the assumption that writes to the page file will prematurely kill your SSD, then you are wrong. If, however, you are doing this to maximize free space on your SSD, then you might have a point - but personally I would prefer to enjoy the speed boost that having the page file in the SSD gives me.
Please understand that having the page file on the SSD *does* decrease its life-span for the simple reason that flash cells have a limited number of write cycles - I am NOT saying it doesn't. However, all SSDs use wear leveling techniques to minimize this problem, based on the free number of cells in the drive *and* the spare area every SSD has. This is one of the reasons why filling an SSD to full capacity is probably *a very bad thing* (you limit the number of empty cells that can be used for wear leveling).
There are a lot of factors to take into consideration when predicting how long an SSD will last - workload, total capacity, size of spare area, etc... - but, for an Intel SSD 520 240 GB drive, Anandtech calculated the maximum number of TB written to it before every cell is exhausted to be around 1010 TB (for an Intel 320 drive with 160 GB, this number is 803 TB).
So, since in 2 years I have written 15 TB to my '240 GB' SSD, at the current usage level and according to the above numbers, my RAID 0 array might just last another 100 years.
The point is, *even* if the lifespan was just 5 years, in 5 years I will have already replaced my SSDs with something else which is faster and cheaper. So there is no point in over-optimizing, the trade off is simple not worth it.