Article ID: 241527
Article Last Modified on 3/1/2007
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4
- Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 5
- Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 6
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT 4.0 Service Pack 1
- Microsoft Windows NT 4.0 Service Pack 2
- Microsoft Windows NT 4.0 Service Pack 3
- Microsoft Windows NT 4.0 Service Pack 4
- Microsoft Windows NT 4.0 Service Pack 5
- Microsoft Windows NT 4.0 Service Pack 6
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT 4.0 Service Pack 4
- Microsoft Windows NT 4.0 Service Pack 5
- Microsoft Windows NT 4.0 Service Pack 6
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft BackOffice Server 4.0
- Microsoft BackOffice Server 4.5
This article was previously published under Q241527
SYMPTOMS
When you monitor the System or Processor Queue Length counter from a remote location, you can observe higher values than when you monitor this counter locally.
CAUSE
This behavior can occur because the Processor Queue Length counter is an instantaneous counter that collects all the threads in the system, and then counts all the ready threads at that instant.
If the system is blocked for some reason, for example, the system is handling a remote procedure call (RPC) network operation, the ready thread count at that instant can build up to a very high number. This high count number is usually temporary, however; as soon as the blocking thread is completed, the ready threads can be processed.
WORKAROUND
To work around this behavior, you can obtain a value if you perform the Performance Monitor logging locally, and then view the log from a remote computer.
Keywords: kbenv kbprb KB241527
