Hello,

We have a considerable large .NET application running in Terminal
Services, where other applications are also used (Office, Reflection,
Web applications).
We are getting major slowdowns at times, where all terminal clients lock
up for a couple of seconds and then come back.
There is also a problem that may be linked to this: our application
sometimes grows really large (Private Bytes and Working Set over 200MB).
However, when monitoring our managed code via profiling, there are some
peaks, but the managed heap consumption is never over 80-100MB. Why this
difference?
We are new to deploying .NET applications in Terminal Server
environments and would like to hear any advice on how to improve the
performance.
Thank you for any help given.

Regards,
paulo

Hello,

in a terminal server environment, you should ngen your assemblies. This
causes the assemblies to be shared among processes in memory, thus removing
pressure from the private bytes heap.

Best regards,
Henning Krause

"paulo" <isf (AT) nospam (DOT) nospam> wrote

Hello Henning,

Thank you for your reply. I forgot to say that our assemblies are
processed with ngen on the Terminal Server machine. So the problem I
reported happens with ngen assemblies.

Regards,
paulo

Henning Krause [MVP - Exchange] wrote:

Hi Paulo,

As for your .NET application, is there any particular operations that
involve some unmanaged component(through interop) which may cause resource
limitation? Based on my research, there are some such issue(performance hit
in terminal service environment) that caused by network or OS specific
problem. Here are some web document about terminal service specific issue:

#Windows Server 2003 Terminal Server Capacity and Scaling
http://www.microsoft.com/windowsserv...tsscaling.mspx

#TS + Citrix Troubleshooting
http://ts.veranoest.net/ts_performance.htm

You can have a look to see whether that help some.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.