zoukankan      html  css  js  c++  java
  • How to Create a Performance Monitor Log for NT Troubleshooting [ZTfrom MS]

    How to Create a Performance Monitor Log for NT Troubleshooting

    Article ID : 150934
    Last Review : November 1, 2006
    Revision : 2.1
    This article was previously published under Q150934
    For a Microsoft Windows 2000 version of this article, see 248345 (http://support.microsoft.com/kb/248345/EN-US/).

    SUMMARY

    This article explains how to create a Performance Monitor log so that engineers can use it to troubleshoot performance problems on a computer running Windows NT.

    MORE INFORMATION

    Creating the Performance Monitor log:
    1. On the View menu, click Log.
    2. On the Edit menu, click Add To Log.
    3. In the Computer field, specify the name of the local computer or a remote computer you want to get a log of. In Objects, add the counters that you want Performance Monitor to log. These counters will change depending on the issue that you are troubleshooting.
    4. Click to highlight the objects that you wish to monitor and then click Add.
    5. Under Options click Log.
    6. Under File Name, name the log.
    7. In Update Time, set the interval according to how long you want to run the Performance Monitor log. If you want to run the log for an extended period of time, you will want to set this update time to an interval much higher than 15 seconds or the log will be very large. If you are going to run the log for only an hour, then 15 seconds will be fine.
    8. Click Start Log. The icon will change to a Stop Log icon once the log is started.
    When you are ready to stop monitoring the selected objects and examine your log file, perform the following steps:
    1. Under Options click Log and then click Stop Log.
    2. In the Options menu click Data from, click Log File, and then click to select the radio button beside the perfmon.log field and locate your log file.

    NOTE: You cannot open a log file simply by clicking File and then clicking Open.
    3. After you open the log file, add the objects and counters that the log has monitored. Do this for each view needed, otherwise the log file's data will not be available.
    If 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 items.

    Memory resource issues:
    Cache
    Memory
    Objects
    Paging file
    Process
    Processor
    System
    Terminal Services (if a Terminal Server)
    For all other resource issues, add additional counters:
    Logical disk
    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
    NOTES
    Disk counters require that you run diskperf -y from the command console and then restart the computer.
    We usually do not capture threads on a terminal server because this counter can consume 80% of a data file.
    You have several options if the computer that is running Perfmon is restarted or goes down while the log is going. You can start a new log, or, if you specify the name of an existing log file, the new data is appended to the end of the log file. It is important to let the engineer know the log was restarted. However, if you are monitoring remotely and the target computer goes down, this does not apply.
    If there are processes that start after the log was started, they will not show up in the beginning of the log. To view different periods in the log, click Edit, click Time Window, and then use the sliding scale.
    If the user logs off, the performance monitor log will stop. You can set up Performance logging as a service, but it is easiest to run Performance Monitor remotely from another Windows NT system.
    For additional information about troubleshooting performance issues, click the article number below to view the article in the Microsoft Knowledge Base:
    175658 (http://support.microsoft.com/kb/175658/EN-US/) Gathering Information for Troubleshooting Performance

    APPLIES TO
    Microsoft Windows NT Workstation 3.5
    Microsoft Windows NT Workstation 3.51
    Microsoft Windows NT Workstation 4.0 Developer Edition
    Microsoft Windows NT Server 3.5
    Microsoft Windows NT Server 3.51
    Microsoft Windows NT Server 4.0 Standard Edition

    Back to the top

    Keywords: 
    kbinfo KB150934
  • 相关阅读:
    笔记本电脑处理器(CPU)性能排行榜
    SQL Server 2008管理工具出现 远程过程调用失败0x800706be解决方法
    Installshield使用教程
    区间DP--凸多边形三角剖分
    树形DP--codevs 1380 没有上司的舞会
    DP练习 巡逻
    DP练习 最长上升子序列nlogn解法
    线段树 求区间连乘——hdu 3074 Multiply game
    模拟算法+栈 HDU 1022
    并查集--CSUOJ 1601 War
  • 原文地址:https://www.cnblogs.com/liangqihui/p/1083551.html
Copyright © 2011-2022 走看看