Re: Stable E8400 OC - stock voltages
It doesn't matter if like me you're using a seperate partition. Remember, although the page file is seen by Windows Explorer as a big "pagefile.sys" it's really just a container for loads and loads of small writes ie RAM being paged out then back in.
Fragmentation performance drop on a page file therefore isn't all that great. Definitely set a fixed size if it's on your System partition and you have plenty of space. If however it's on a small drive, letting it grow as needed up to the max of the drive is fine. The page file will also force itself to shrink should a program need to save to disk.
Optimum configuration for a page file is to have two identical sized page files on two hard drives/non RAID SSD's. This is because from XP upward a certain amount of parallelism was introduced. Sort of like software RAID but just for the page file.
You can also tidy up any excess fragments the page file may get into by using PageDefrag. It's so good, Microsoft bought it. download it from here: PageDefrag You can choose to defrag on every boot if you wish.
Above all, the over riding factor is that if you set a reasonable size for the initial page file quantity, it will seldom grow. Mine only ever does when using Photoshop and sometimes HandBrake (H264 encoding). Usually on a 64bit system with 4GB of RAM, the page file isn't heavily used.
There are many myths about the page file, like having to set 1.5x RAM amount. This isn't true. You may think that one needs enough to page out all installed RAM, but you don't. The more physical RAM you have the less swap space is necessary. Linux has it correct, partitioning a seperate section of the HDD with an optimized file system just for swap space. It will also use every last drop of RAM before paging anything.
It doesn't matter if like me you're using a seperate partition. Remember, although the page file is seen by Windows Explorer as a big "pagefile.sys" it's really just a container for loads and loads of small writes ie RAM being paged out then back in.
Fragmentation performance drop on a page file therefore isn't all that great. Definitely set a fixed size if it's on your System partition and you have plenty of space. If however it's on a small drive, letting it grow as needed up to the max of the drive is fine. The page file will also force itself to shrink should a program need to save to disk.
Optimum configuration for a page file is to have two identical sized page files on two hard drives/non RAID SSD's. This is because from XP upward a certain amount of parallelism was introduced. Sort of like software RAID but just for the page file.
You can also tidy up any excess fragments the page file may get into by using PageDefrag. It's so good, Microsoft bought it. download it from here: PageDefrag You can choose to defrag on every boot if you wish.
Above all, the over riding factor is that if you set a reasonable size for the initial page file quantity, it will seldom grow. Mine only ever does when using Photoshop and sometimes HandBrake (H264 encoding). Usually on a 64bit system with 4GB of RAM, the page file isn't heavily used.
There are many myths about the page file, like having to set 1.5x RAM amount. This isn't true. You may think that one needs enough to page out all installed RAM, but you don't. The more physical RAM you have the less swap space is necessary. Linux has it correct, partitioning a seperate section of the HDD with an optimized file system just for swap space. It will also use every last drop of RAM before paging anything.
Comment