akdreaming
asked on
PageFile is HUGE.
When I go to the task manager on one of our servers, the PF Usage is showing 11.5GB. The RAM on the system is 16GB. Also, when we have had to reboot the server, it is staying in the applying computer settings for an awful long time. Are these two related, and is there a way to reduce the usage?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The applying computer settings is possibly due to your AD GPO. Do you know what settings are enabled on your GPO?
Also, if you have the feature "always wait for network" GPO option set, this can also cause this effect.
Also, if you have the feature "always wait for network" GPO option set, this can also cause this effect.
I don't get it. The PF usage graph is not the Pagefile. 11.5 GB used on a 16GB RAM system may be completely normal if it's running all kinds of database services. The server is just utilizing the RAM it has, and there's no need to decrease usage (I'd even recommend against it).
One other obvious question: is the server a domain controller? The 'Applying computer settings' stage usually takes a healthy while on DCs.
The 'Always wait for network' setting is here, if you're interested:
Computer Settings | Adm. templates | System | Logon | Always wait for the network at computer startup and logon
One other obvious question: is the server a domain controller? The 'Applying computer settings' stage usually takes a healthy while on DCs.
The 'Always wait for network' setting is here, if you're interested:
Computer Settings | Adm. templates | System | Logon | Always wait for the network at computer startup and logon
The label says "PF Usage" but that is not what it is showing. This is actually the Commit Charge. This is not RAM usage, actual pagefile usage, or any combination of the two. It isn't a measurement of anything that physically exists. It can be thought of as potential pagefile usage. Actual pagefile usage will typically be much lower. And much of the data that is in the pagefile will also be in RAM. There is nothing in Task Manager that shows actual pagefile usage.
The Commit Charge has little influence on performance. You just need to be certain that it is well under the Commit Limit.
It is really unfortunate that Microsoft chose to label this gauge "PF Usage". It has been the cause of an enormous amount of confusion and has resulted in a great deal of unwarranted criticism of Windows memory management.
The Commit Charge has little influence on performance. You just need to be certain that it is well under the Commit Limit.
It is really unfortunate that Microsoft chose to label this gauge "PF Usage". It has been the cause of an enormous amount of confusion and has resulted in a great deal of unwarranted criticism of Windows memory management.
ASKER
These comments are helping me tremendously with my troubleshooting. We are still looking into it.
It looks like the issues we are having may have nothing to do with the PF Usage. However, I have learned a lot.
It looks like the issues we are having may have nothing to do with the PF Usage. However, I have learned a lot.
Make sure you check out in your network settings to uncheck register in DNS for the primary nic that you are using. This is one of the gotchas that I have found that has this problem. Just go the network properties of the NIC and uncheck the Register in DNS option. This may help you out.
scameron447: I definitely don't agree with that advice, especially since we have zero information on the server. Bad idea on a domain controller!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Many good tidbits of information. It looks like the problems we are having are not related to the PF. We are working with our software vendor. Thanks again!
The paging file issue is mostly explained above by athibodeau. As for the server staying a while in the applying computer settings, it may also be a DNS issue because at that step is when the server applies the domain policies.