Re: Memory problems with Terminal Server 2003
- From: "TP" <tperson.knowspamn@xxxxxxxxxxxxxxx>
- Date: Thu, 15 Jan 2009 07:07:04 -0500
Hi,
The number you see in Task Manager in the "PF Usage" box is *not* the current Page File usage, nor is it the current size of your Page File. It is the current total amount of Committed virtual memory.
I will simplify my descriptions a bit. Think of the above number as the total amount of memory allocated by the programs you have running on the server. Memory is a combination of "real" physical RAM as well as the paging file(s) located on hard disk.
For example, if you have a server with 32GB of physical RAM (and x64 windows version), and you have a 16GB page file, then you have a total of 48GB of memory for use by programs.
When the system does not have enough physical RAM to hold all of the recently used allocated virtual memory, it will copy pages of memory to and from the page file as needed. This process is very slow (due to hard drive read/write speed compared to RAM read/write) and is something to avoid as much as possible.
The way to avoid using the page file is to have plenty of physical RAM for the expected/measured load. Plenty means having substantially more than the maximum value you observe in the PF Usage box. Having lots of extra helps with caching files as well.
If you are regularly seeing numbers that are twice your installed physical RAM then your performance problems are almost certainly due to the paging to/from hard disk described above.
Memory is relatively inexpensive now. The 32GB used in the example above is Tier 1 and costs $1,360. Your hardware and windows version needs to be able to support the amount of RAM you plan to install.
If you want to see the current amount of page file in use at a given moment in time you can use the pstat.exe utility.
Thanks.
-TP
MH wrote:
I have this exact same problem. Outlook is killing me. It used to.
utilize around 80mb and now it is up to 150mb per user. Whether it is
shared or not is of course a different issue...I would really like to
know how to fix this...
In reference to this statment:
When looking at task manager it is helpful to add the VM
Size column as well. As a general rule, on a dedicated TS
try to keep your PF Usage (Commit Charge) number
below the total amount of physical RAM.
Is there a particular reason for this? Mine is double...I always
heard that a page file should be 1-2 times that of memory.
- References:
- Prev by Date: Re: Audio Redirection in Windows Terminal Server 2008
- Next by Date: Re: Preserve TS Users Profiles
- Previous by thread: Re: Memory problems with Terminal Server 2003
- Index(es):
Relevant Pages
|
