earls
03-20-2009, 03:13 PM
Setup: Two PE32GS25SSDR in RAID 0; 4GB of RAM; One 250GB SATA II HDD; ~2GB Page File currently on the SSDs.
The computer is specifically used for gaming, internet access.
Options:
1. Leave the page file on the SSD drives.
I've recently been educated about the degradation in performance of SSD drives once all of the pages/blocks of the SSD have been filled.
Apparently, although the specific speed of writing to a page is the same, if the page is already filled, there is a delay while the page is overwritten. I figure with the page file on the SSD, all of the pages/blocks on the SSD are going to be quickly filled (if not already) as, on average, 1.5 GB is written to drive when the page file is filled while gaming.
I guess the real question is, does the page file use the same (allocated) pages/blocks each time, or does it use the typical SSD logic: Fill up the drive first, then overwrite?
2. The second option is to put the page file on the HDD.
Depending on the answer of the question above, this seems like the best course of action... It maintains a decent page file access speed (though not on par with the SSDs), but does not degrade the performance of the SSDs overtime.
3. Finally, I can disable the page file completely.
From my understanding, this virtually relegates the page file to RAM. Some have reported problems with specific applications, and apparently this option isn't "native" to Windows.
Some argue the page file is "wasting" the RAM, it seems to me however, that in most cases I have at minimum one GB of unallocated RAM just sitting there... So...?
I was hoping to get some input from Patriot.
Thanks!
The computer is specifically used for gaming, internet access.
Options:
1. Leave the page file on the SSD drives.
I've recently been educated about the degradation in performance of SSD drives once all of the pages/blocks of the SSD have been filled.
Apparently, although the specific speed of writing to a page is the same, if the page is already filled, there is a delay while the page is overwritten. I figure with the page file on the SSD, all of the pages/blocks on the SSD are going to be quickly filled (if not already) as, on average, 1.5 GB is written to drive when the page file is filled while gaming.
I guess the real question is, does the page file use the same (allocated) pages/blocks each time, or does it use the typical SSD logic: Fill up the drive first, then overwrite?
2. The second option is to put the page file on the HDD.
Depending on the answer of the question above, this seems like the best course of action... It maintains a decent page file access speed (though not on par with the SSDs), but does not degrade the performance of the SSDs overtime.
3. Finally, I can disable the page file completely.
From my understanding, this virtually relegates the page file to RAM. Some have reported problems with specific applications, and apparently this option isn't "native" to Windows.
Some argue the page file is "wasting" the RAM, it seems to me however, that in most cases I have at minimum one GB of unallocated RAM just sitting there... So...?
I was hoping to get some input from Patriot.
Thanks!