I have some poor performing servers. All are 2003 64bit. 2 are virtual and 5 are physical but they all experience the same problem. They are TS servers. THey get very sluggish or with freeze for periods of time. Sometimes 45
seconds. There is not a clear processor or memory or disk bottleneck. I have been gathering data on Interrupts and DPC's but nothing I read tells me how to know if they are high or not.

Here is an example of a single processor core I think.
I get DPC's queued/sec as high as 400 per processor instance (core?) within perfmon.
For Interrupts/sec I can be as high as 5k a sec per processor instace.

For all I know this is no problem at all. Any direction is appreciated.
Thanks.

Need to support users over the internet? click here try our remote control online beta

Hello,

---I have been gathering data on Interrupts and DPC's but nothing I read tells me how to know if they are high or not.

That's true. No one can tell if a counter is too high or not in your case because we have very different hardware/software environment. You shall establish a performance baseline of your terminal server first so that in the future you can compare to determine
if the server is in good state.

Establishing a Performance Baseline

http://technet.microsoft.com/en-us/library/cc781394(v=WS.10).aspx

Terminal Server Capacity Planning

http://technet.microsoft.com/en-us/library/cc786809(v=WS.10).aspx


Some common counters to monitor are as following.

Network Interface (all instances)
- Bytes Received/sec
- Bytes Sent/sec
Paging File (all instances)
- % Usage*
Processor (all instances)
- % User Time*
- % Privileged Time
Server
- Files Open*
- Pool Paged Bytes
System
- File Data Operations/sec*
Indexing Service (all instances)
- Index Size
- Files to be indexed
Memory
- Available MBytes*
- Page Faults/sec*

Need to support users over the internet? click here try our remote control online beta

Hello,

---I have been gathering data on Interrupts and DPC's but nothing I read tells me how to know if they are high or not.

That's true. No one can tell if a counter is too high or not in your case because we have very different hardware/software environment. You shall establish a performance baseline of your terminal server first so that in the future you can compare to determine
if the server is in good state.

Establishing a Performance Baseline

http://technet.microsoft.com/en-us/library/cc781394(v=WS.10).aspx

Terminal Server Capacity Planning

http://technet.microsoft.com/en-us/library/cc786809(v=WS.10).aspx


Some common counters to monitor are as following.

Network Interface (all instances)
- Bytes Received/sec
- Bytes Sent/sec
Paging File (all instances)
- % Usage*
Processor (all instances)
- % User Time*
- % Privileged Time
Server
- Files Open*
- Pool Paged Bytes
System
- File Data Operations/sec*
Indexing Service (all instances)
- Index Size
- Files to be indexed
Memory
- Available MBytes*
- Page Faults/sec*

Need to support users over the internet? click here try our remote control online beta