Troubleshooting Server Hangs - Part One
Wednesday, 26 September 2007 by Michel Roth
Terminal Servers are often the victim of tuning. This is because by their very nature they often need to be tuned to handle the workloads they need to deal with. Sometimes a server is "overtuned" actually creating a new bottleneck (or rather DoS) in stead of solving a performance problem.

This gets especially tricky when the kernel memory is being tuned. This is something that is not uncommon to do. Usually the available kernel memory is the limit you encounter when trying to get the maximum amount of users on a server. It's tempting to start tuning kernel mode memory so that the subcomponents of the kernel memory are spread out perfectly so you get the maximum amount of users on a server. However, when the kernel memory is "overtuned" or tuned in the wrong way, the bits really start to hit the fan.

Troubleshooting kernel memory problems can be quite a hassle. The Windows Performance team has an interesting blog entry up on this exact subject: Troubleshooting Server Hangs - Part One.

Related Items:

Should I Use The /3GB In My BOOT.INI With Virtual Server (29 May 2006)
One reason Why Windows Server 2008 Terminal Server Will Allow You To Get More Users On A Box (10 February 2008)
Patch Vista?s Kernel to Address more than 4 GB of Memory (25 June 2009)
Windows CE 6.0 Has Been Released To Manufacturing (18 September 2006)
Microsoft Rolls Out Windows CE 6 (9 May 2006)
Performance Monitoring On TS: Memory Management (15 September 2009)
Multi-monitor support For Citrix ICA Sessions (13 April 2006)
Memory overcommit in production? (12 January 2010)
What's going On With My Pagefile ... And The Rest Of My Server? (15 May 2007)
Developing The TS Multi-User Kernel (10 January 2008)
Comments (0)
Show/Hide comment form