|
|
Question : Problem: Page File usage with plenty of RAM to spare
|
|
This particular server is running Windows Server 2003. This server is accessed daily by 30 or so users, and is loaded with 6 gigs of RAM. The thing that puzzles me is that the task manager tells me that I have around 3 gigs of physical RAM available, but it still uses the page file, and lots of it. I have the page file set to around 13 gigs, and at times, task manager will say that 4-5 gigs is being used. This concerns me, as I believe it may have a negative effect on the performance of this server. Would it be best to completely eliminate the page file, or is there a misconfigured parameter that tells the machine to access the PF instead of the RAM? Thanks
|
Answer : Problem: Page File usage with plenty of RAM to spare
|
|
The pagefile is necessary. This is because the OS is a virtual memory machine. Regardless of how much RAM the system has, the OS will always use some of the page file to move rarely used OS routines into and will commit virtual memory to processes even though they are not runnig. Even with 4 gig of RAM and doing nothing but sitting there, the OS uses the page file because thats the way the OS was written. If you try and eliminate the page file you will run into problems. Its really interesting when you are only using a couple a hundred meg of RAM in a multi-gig box and get an out of memory error.
|
|
|
|