Como usar o monitor da confiabilidade 2008 e do desempenho do usuário de Windows
A confiabilidade e o desempenho monitoram snap-in permitem-no de monitorar o desempenho do usuário em real - tempo. Você pode monitorar a ferragem e o desempenho da aplicação e criar alertas do ponto inicial e relatórios do desempenho. Nos termos de definir o desempenho e a confiabilidade, o desempenho descreve como rapidamente o usuário termina as tarefas que deve realizar. A confiabilidade, na uma mão, é mais uma medida de como frequentemente o usuário executa exatamente porque você esperaria com relação a sua configuração.
O monitor da confiabilidade e do desempenho snap-in fornece também o acesso ao monitor do desempenho, que estava disponível no usuário 2003 de Windows, e ao monitor novo da confiabilidade. O monitor do desempenho permite-o de adicionar contadores a rapidamente vê a informação real-time da ferragem tal como o tempo de processador dos por cento e vê também a informação relacionada aos serviços de sistema tais como o HTTP (em um web server).
O monitor da confiabilidade fornece uma carta da estabilidade do sistema que possa ser usada ver rapidamente a informação específica sobre a ferragem, a aplicação, e as falhas de Windows. Você pode estalar sobre uma data da carta, que funcione ao longo do x-axis da carta e v então os vários relatórios da estabilidade do sistema relacionados aos alertas e às falhas. O monitor da confiabilidade, que, de fato, fornece algum do mesmo tipo de informação que você poderia recolher do visor do evento, é discutido mais tarde na hora.
Obviamente, a confiabilidade e o monitor do desempenho fornecem os muitos da informação potencial relacionados a como um usuário está executando nos termos da ferragem e do software (sistema se operando including). O que você está tentando realmente fazer quando você monitorar o desempenho do usuário é identifica bottlenecks potenciais do desempenho (diga o processador central ou a movimentação dura). Quando você mede a confiabilidade, você está procurando coisas como os excitadores de dispositivo que não inicializaram ou os serviços que tiveram que parar e reiniciar. A confiabilidade relaciona-se frequentemente à configuração do usuário melhor que a configuração de ferragem, como o desempenho.
Você pode abrir o monitor da confiabilidade e do desempenho no gerente do usuário (começo, monitor administrativo das ferramentas, da confiabilidade e do desempenho). Expanda o nó diagnóstico e selecione então o nó da confiabilidade e do desempenho.
Você pode também funcionar o monitor da confiabilidade e do desempenho snap-in no MMC (começo, monitor administrativo das ferramentas, da confiabilidade e do desempenho
A placa da vista do recurso do monitor da confiabilidade e do desempenho fornece-o com um olhar rápido no uso do processador central, do disco, da rede, e da memória no usuário. Real-time counters at the top of the window show you how each of these resources is currently affected by demand on the server from such things as user access, resources served to users, and other processes running on the server that are related to the various roles you have assigned the server.
Below the Resource View graphs is the Resource View details area. By default, all the Resource details are closed and show a counter that provides the running data points that are shown in the associated graph.
You can expand each of the Resource views to view the details related to a particular resource such as the CPU resource, which measures the total percentage of CPU capacity currently in use. When you expand the CPU resource, you are in the Resource Overview details (for CPU capacity), which provides a detail table.
Let's look at each of the resources measured in the Reliability and Performance Monitor and what kind of details are provided when you look at the expanded view details for a particular resource. The Resource view provides the following information:
• CPU— The total percentage of CPU use is displayed in green. The CPU Maximum Frequency is displayed in blue. The details table contains the following:
Image— Application using the CPU
PID— The application instance's process ID
Description— The application name
Threads— Active threads from the application instance
CPU— CPU cycles active from the application instance
Average CPU— Average CPU load (over the last 60 seconds) from the application instance
The PID or process identifier is the unique number the operating system assigns to a process. A thread is part of an application that can execute independently.
• Disk— The total input/output (current) is displayed in green. The percentage for the highest active time is displayed in blue. The details table contains the following:
Image— Application using the disk
PID— The application instance's process ID
File— The file read/written by an application
Read— The current read speed (in bytes/minute) for the data by an application
Write— The speed (bytes/minute) at which the application is writing data
IO Priority— The I/O task priority for the application
Response Time— Disk response time in milliseconds
• Network— Displays the total network traffic (Kbps) in green and the network capacity percentage currently in use in blue. The details table contains the following:
Image— Application using the network resources
PID— The application instance's process ID
Description— The application name
Address— The network address (IP address, FQDN name, or computer name) with which the local computer is exchanging information
Send— The data currently being sent from the local computer (as sent by the application named in the Image line)
Receive— The amount of data currently being received (bytes/minute)
Total— Total bandwidth used (that is, sent and received) in bytes/minute by the application
• Memory— Displays the hard faults per second in green and the physical memory currently in use percentage in blue. The details table contains the following:
A hard fault or page fault is basically when data requested by the application instance is not in real memory and so must be retrieved from the paging file and loaded into memory.
Image— Application using the network resources
PID— The application instance's process ID
Description— The application name
Hard Faults/Min— Hard faults (per minute) resulting from the application instance; a lot of hard faults would indicate that your server's memory is becoming a performance bottleneck
Working Set (KB)— The amount of memory (in kilobytes) currently being used by the application instance
Shareable (KB)— The amount of memory in the working set that may be available to other applications.
Private (KB)— The amount of memory in the working set reserved for the application instance
Obviously, the Resource view details provide a lot of information. But the key to using this information really lies in the fact that server performance can be affected in a negative way by two things: hardware problems and software problems.
The typical hardware bottlenecks for a server are the CPU, disks, network adapter (or adapters), and memory. The Reliability and Performance Monitor provides graphs for these hardware components because they can often be the reason the server is underperforming.
If the problem isn't directly related to a hardware malfunction, the problem can be a software issue that is monopolizing one of the key server hardware components, such as the CPU or the network adapter. Having quick access to the information related to the application instance enables you to potentially identify a malfunctioning software entity. So, although you can gain more specific real-time data using the various counters available in the Performance Monitor and more details related to server hardware and software events that are logged in the Event Viewer, the Reliability and Performance Monitor is definitely a quick way to survey a server's health.
The Reliability Monitor, a new tool provided by the Reliability and Performance Monitor snap-in, provides a system stability chart that enables you to view events related to software, application, and hardware failures. It provides quick access to "bad" events in a timeline, making it a useful addition to server troubleshooting, particularly when used with Event Viewer data.
Written by magakos. Read more great feeds at is source WEBSITE
no comments.
Read more articles on MIcrosoft Windows Server 2008 and otherSoftware.
- [+] Digg: Feature this article
- [+] Del.icio.us: Bookmark this article
- [+] Furl: Bookmark this article
