• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Question about pagefile and hiding it?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Fr3@k3r

Member
What Should The Paging File Size Be?

i threw my pagefile for my os onto another drive, now is there some way i can make it hidden but stil active? i have partition magic 8.5 installed..

and also..

i have 1024 (1gig) installed of real memory.. i have a 5gb partition for my pagin file should i throw my paging file into a size of????

what it is now, 1533-5000 ... any recomendations?
 
Last edited:
With that ammount of memory, you hardly need any pagefile. If I'm not mistaken, putting it on another partition and continuing to use it will decrease performance. Personally, I'd keep it on my C:\ and shrink it to about 256 MB and leave it that way. If you haven't tried Diskeeper, you may want to check it out. There are some powerful tools included that can also help with configuring your pagefile. It's also a great defrag tool with many other options. I use ver 9 and wouldn't be without it.
 
snafumaster said:
With that ammount of memory, you hardly need any pagefile. If I'm not mistaken, putting it on another partition and continuing to use it will decrease performance. Personally, I'd keep it on my C:\ and shrink it to about 256 MB and leave it that way. If you haven't tried Diskeeper, you may want to check it out. There are some powerful tools included that can also help with configuring your pagefile. It's also a great defrag tool with many other options. I use ver 9 and wouldn't be without it.

actually putting it on another partition away from your OS partition increases performance.. microsoft even said that performance increases when moves to another drive..
 
The pagefile on a seperate disk should increase performance, but on another partion on the same disk as the rest of the OS it will decrease performance.
 
i have a 5gb partition for my pagin file should i throw my paging file into a size of????

The pagefile should not be in a partition of its own. On a seperate drive it is not that big of a deal, but it should be on the least-used drive and the most-used partition.

As for the size, just observe PF usage using perfmon after running your most intensive applications. Then set the initial size 4x the observed usage. The max should be set 2x this number.

actually putting it on another partition away from your OS partition increases performance.. microsoft even said that performance increases when moves to another drive..

Wrong. When you have the pagefile on a seperate partition then other data it increases your average seeking distance, thus decreasing performance. Seek time is everything when it comes to performance. This is also why you should not split OS and applications.

The pagefile should be on the least-used drive and the most-used partition as I said above for best performance.
 
BrutalDrew said:
The pagefile should not be in a partition of its own. On a seperate drive it is not that big of a deal, but it should be on the least-used drive and the most-used partition.

As for the size, just observe PF usage using perfmon after running your most intensive applications. Then set the initial size 4x the observed usage. The max should be set 2x this number.



Wrong. When you have the pagefile on a seperate partition then other data it increases your average seeking distance, thus decreasing performance. Seek time is everything when it comes to performance. This is also why you should not split OS and applications.

The pagefile should be on the least-used drive and the most-used partition as I said above for best performance.

i have it on a backup drive that has been split into 2 pagin file partitions... its a 10gb drive split into 2 partitions... so i can dbl boot xp pro and longhorn beta
 
the pagefile is accessed by the OS, regardless of 'who' is using the puter, period. As far as 'seeing' the pagefile in windows explorer, you just have to set the folder properties to not show system files, but this is by user profile, by default, XP 'hides' sytem files for users.
 
Fr3@k3r said:
i want to hide it because i dont want anyone that uses me computer to be able to access it.. the page file partition is accessible to anyone in my family who is on my computer.. i just want to make it non accessible but still useable

??????? What else is on the partition you're trying to hide? Do you think your pagefile is porn or what?
 
Fr3@k3r said:
no i just dont want anyone to think thats a storage partition and use it to store files that dont need to be there :(

Well, like BrutalDrew said, if it's XP you should have it on the OS partition, or on a separate drive entirely. If you must have it in it's own partition just size the partition accordingly.
 
cw823 said:
Well, like BrutalDrew said, if it's XP you should have it on the OS partition, or on a separate drive entirely. If you must have it in it's own partition just size the partition accordingly.

but you didnt read?

#1 - is on its own drive
#2 - is on a 5gb partition on that drive
#3 - the only other thing on that drive is another 5gb partition with Longhorn beta pagefile which only gets used when i boot into longhorn so its dormant when i boot into xp pro
 
Fr3@k3r said:
but you didnt read?

#1 - is on its own drive
#2 - is on a 5gb partition on that drive
#3 - the only other thing on that drive is another 5gb partition with Longhorn beta pagefile which only gets used when i boot into longhorn so its dormant when i boot into xp pro

As a general rule you should make your pagefile 1.5 times your actual RAM. Anything more than that would be overkill. Could create two 1.5G partitions and a third for some kind of data storage.
 
Officially MS recommends that it be 1.5 the ammount of your actual physical ram. But as it has been said, with a gig of ram, you are really not going to have much of a problem. I don't think that MS had these large ram capacities in mind when they came up with that guideline, but I could be wrong.
 
Back