techdept
asked on
High Pages/sec on 2003 Terminal Server
Experiencing some odd memory behavior on a Windows Server 2003 64bit ENT box running Terminal Services. The machine has 72GB of memory, showing plenty available in Task Manager. Yet when running perfmon the only counter which spikes quite consistently are the page Reads/sec and Page input/sec. CPU and disk queue lengs remain consistently low. Can anyone shed some light? Also this being one of our first boxes which this amount of memory I was not 100% on page file sizing. Is it still rule of thumb to create a page file 1-1.5x physical memory? Should I be configuring a 72-108GB page file? Is this too big? Thanks for any help
ASKER
The majority of the users on the server are running a .Net application with SQL Database (hosted on dedicated server) I would think that .net would utilize the available memory. The main executable absorbs anywhere from 50-300MB of memory per user's instance.
well i don't know if this is retarded, but i have 16gbs of ram allocated to my terminal server, and i turned off paging...runs just fine
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
With that much physical memory, I wouldn't worry about creating a large page file.