Solved

High Pages/sec on 2003 Terminal Server

Posted on 2011-02-22
4
1,126 Views
Last Modified: 2012-05-11
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
0
Comment
Question by:techdept
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 34

Expert Comment

by:Paul MacDonald
ID: 34952368
Is it possible you're running a legacy application, something that doesn't know how to use large amounts of memory?

With that much physical memory, I wouldn't worry about creating a large page file.
0
 

Author Comment

by:techdept
ID: 34952484
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.
0
 
LVL 3

Expert Comment

by:rxdeath
ID: 34956563
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
0
 
LVL 34

Accepted Solution

by:
Paul MacDonald earned 500 total points
ID: 34960660
Hmm - I'd thought I'd replied already...

Yes, a .Net application shouldn't have any trouble using the RAM.  Also, with that much RAM, I wouldn't worry about using the traditional values for the swap file.  

What are the values for the Pages Read/Pages Write?  Are they high as a percentage, or just higher than other values you're monitoring?  I would exect some page swapping just as a matter of course and, unless you're spiking to some really high value, the activity can probably be ignored.  Like [rxdeath], you could just turn off paging and see if there's an impact on performace.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Learn about cloud computing and its benefits for small business owners.
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question