Article ID: 175658 - Last Review: November 1, 2006 - Revision: 2.2 How To Gather Information for Effective Troubleshooting of Performance IssuesThis article was previously published under Q175658 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
On This PageSUMMARY
This article explains how to gather information so that Microsoft Support
Professionals can troubleshoot performance problems on a computer running
Windows NT. Please read all steps as you will be asked to provide
information from several tools when contacting a support professional for assistance.
MORE INFORMATION
The basic tool used for troubleshooting performance issues is Performance
Monitor. Follow the steps below to prepare for collecting performance
information:
Prior to Creating a Performance Monitor Log
Creating the Performance Monitor LogRun Performance Monitor from the following location:
150934
(http://support.microsoft.com/kb/150934/EN-US/
)
How to Create a Performance Monitor Log for NT Troubleshooting
In cases where the User Interface (UI) of the server in question is hanging
or not responding, run Performance Monitor from another computer running
Windows NT Server or Workstation.
The counters recommended in the article above will change depending on the problem that you are troubleshooting. See the "Recommended Performance Objects" section below or consult the Microsoft support professional for suggested objects to monitor. Recommended Performance ObjectsIf you are troubleshooting a performance issue or an issue that looks like a memory leak, the objects that Performance Monitor should log include, but are not limited to, the following:For memory leaks:
Cache
For all other resource issues, add additional counters:
Memory Objects Paging file Process Processor System Terminal Services (if a Terminal Server)
Logical disk
In addition, the smaller the update interval, the larger the log file, so
check to make certain there is sufficient disk space available on the
computer running Performance Monitor.
NBT Connections Network interface Physical disk Redirector Server Server work queues Thread (do NOT capture if a terminal server) All Terminal Server counters (if a Terminal Server) All Protocol counters bound to network adapters Allow Performance Monitor to run a minimum of three days unless you have been instructed otherwise. Do not log off of the computer where you are running Performance Monitor as this will close out Performance Monitor. Minimize Performance Monitor if preferred and if needed lock the screen on this computer. After Creating the Performance Monitor Log
| Article Translations
|
Back to the top
