Windows Performance Monitor

Front-end time is a dynamic target monitoring, the application needs to consider the large data volume and multi-user concurrency, the performance of the system is an important measure of the implementation of the solution. Here is a simple record of performance monitoring and simple analysis in Windows.

General operating system performance mainly related to the main problems are: Processor usage, memory footprint, disk i/0 operations, and network traffic.

To view Windows performance, in most cases through Windows Task Manager, you can eject task Manager by typing: taskmgr in the command line. Task Manager can view: CPU usage, memory usage, and network traffic.

Using Windows Task Manager is intuitive and the UI works fine. However, there are some drawbacks, such as: The performance parameters can be referenced is not comprehensive, can not record performance for a long time and no performance report log and so on.

Perfmon Performance Monitor is a performance tool that comes with windows that provides basic data about the operating system, such as memory, CPU, IO, network-related information, and features such as graphical reporting, logging, tracking, and alerting. Can be entered through the perfmon of CMD.

Perfmon counters are divided into four main types: Processor performance counters, memory performance counters, disk performance counters, and network performance counters.

The object here refers to a performance monitor object. There will be multiple counters for any one object-[counter name]-and there may be multiple instances: This is true when there are multiple processors in the system or if the system has more than one hard drive.

Here are a few common counters, introduction format: [Object]: [Counter name] [explanation/description]

Processor performance Counters

Processor objects focus primarily on the CPU in the system. Note that some systems have multiple CPUs, and the counters will have a separate instance for each CPU to display.

Processor:% Processor Time

The current processor time for all processes [i.e. CPU utilization], if the value continues to exceed 95%,cpu is the bottleneck. % Processor time value =100%-idle process ratio [that is: idle thread]],CPU It's okay to execute a free thread.

processor:% User Time

is the system non-core operation consumes CPU time, if it is a database server, the reason why the%user time value is very likely is the database sorting or function operation consumes excessive CPU, at this time can consider the database system optimization.

Memory Performance Counters

Memory:available Mbytes

The amount of memory that can be used. If the indicator's data is small, there may be a memory problem with the system

Memory:pages/sec

Indicates the number of pages fetched from disk due to hardware page faults, or the number of pages written to disk to free working set space due to a page fault. Generally if the pages/sec continues above hundreds of, then you should study the paging activity further. There may be a need to increase memory to reduce the need for page breaks. A large value of pages/sec does not necessarily indicate a memory problem, but may be caused by a program running a memory-mapped file. A high ratio of counters indicates excessive paging.

Memory:page faults/sec and Memory:page reads/sec counters measure memory performance.

Page faults occur when the virtual memory page referenced by the process is not in memory, and Memory:page Faults/sec represents the number of page faults. If a page is already in main memory, or if it is being used by another process that is sharing this page, then the page will not be paged in from disk.

Memory:page Reads/sec is a read disk that extracts the number of pages required to resolve page faults. In general, these two counters reflect the frequency of access to the disk, and the lower the value, the less the response time.

Network Performance counters

Main View Network Interface object

Network interface:bytes received/sec

How many bytes data received per second, combined with bytes total/sec analysis

Network interface:bytes sent/sec

How many bytes data per second are sent, combined with bytes total/sec analysis

Network interface:bytes total/sec

The total number of machines accepted and sent bytes recommended not to exceed 50% of the bandwidth

Network interface:packets/sec

The number of packets per second, according to the actual data volume size, no recommended threshold, the data combined with bytes total/sec analysis

Performance analysis

1. Memory Analysis method

Memory analysis is used to determine if the system has a memory bottleneck and whether it needs to improve the performance of the system by means of additional memory.

The counters that memory analysis needs to use: The Memories category and the counters for the physical disk category. The main methods and steps of memory analysis:

(1) First view memory:available MBytes indicators

If the indicator data is small, the system may have a memory problem, you need to continue the following steps to further analysis.

(2) Note the values for memory:pages/sec, Pages read/sec, and page faults/sec

The operating system uses the disk better to improve the amount of memory available to the system or to improve its efficiency. These three metrics directly reflect the frequency with which the operating system is swapping disks.

The PAGES/SEC value persists above hundreds of and there may be a memory problem. A pages/sec value does not necessarily indicate a memory problem, possibly caused by a program running a memory-mapped file.

Page Faults/sec Describes how many pages fail per second, and the more page failures, the more times the operating system reads to memory. You need to see the count value for pages read/sec, which has a threshold of 5 and if the count is more than 5, you can determine a memory problem.

(3) Analyze performance bottlenecks based on the value of the physical disk counter

The analysis of the physical Disk counter object includes analysis of page reads/sec and%disk time and aerage disk Queue length. If pages read/sec is low and the value of%disk time and average disk Queue length is high, there may be a disk bottleneck. However, if the queue length increases while the pages read/sec is not lowered, then there is insufficient memory.

2. Processor Analysis method

(1) First look at the count value of the System:%total Processor time performance counter

The value of this counter reflects the overall processor utilization of the server, which reminds the average utilization of all CPUs for multiprocessor systems. If the value continues to exceed 90%, it means that the entire system is facing a processor bottleneck and needs to increase performance by increasing the processor.

Note: In multiprocessor systems, the data itself is small, but the put direct load condition is extremely uneven and should be seen as a system-generated processor bottleneck.

(2) Second view of Processor per CPU: \%processor time and Processor:\%user time and processor:\%privileged time

Processor:%user is the CPU time consumed by non-core operation of the system, if the value is large, it can be considered whether the friendly algorithm can be used

Lower this value. If the server is a database server, the reason why the Processor\%user time value is large is likely to be that the database is sorted or the function operation consumes too much CPU, so you can consider optimizing the database system.

(3) Research system processor bottleneck

View the value of the System:processor Queue Length counter when the value of the counter is greater than the total number of CPUs + 1 o'clock, indicating that the processor is blocked. When the processor's%process time is high, it is generally blocked with the processor, but when processor blocking occurs, Processor:%process time Meter

The value of the digital device is not necessarily large, you must find the cause of the processor blocking.

3. Disk I/O analysis method

(1) Calculate the number of I/Os per disk

The number of I/Os per disk can be used to compare the I/O capability of the disk, and if the number of per-disk I/Os computed exceeds the nominal I/O capability of the disk, there is a real disk performance bottleneck.

(2) analysis in combination with processor:privileged time

If the physical disk counter, only%disk time is large, the other values are relatively moderate, the hard disk may be a bottleneck. If a few values are large and the values continue to exceed 80%, a memory leak can occur.

(3) Analysis based on disk Sec/transfer

In general, the definition of this value is less than 15ms excellent, between 15~30ms is good, between the 30~60ms is acceptable, more than 60ms need to consider the replacement of hard disk or hard disk RAID mode.

4. Process Analysis Methods

(1) Viewing the process:%processor time value of a process

The%processor time of each process reflects the processor times consumed by the process. By comparing the processor time consumed by different processes, you can see which process has consumed the most processor time in the performance test process, which can be optimized for the application accordingly.

(2) View the page failures generated by each process

It is possible to determine which process produced the most page failure by the ratio of the page invalidation (obtained by the Process:page failures/sec counter) and the System page failure (which can be obtained by the Memory:page failures/sec counter) generated by each process. This process is either a process that requires a lot of memory, or it is a very active process that can be focused on.

(3) Understanding the process:private of the process Bytes

Process:private bytes refers to the current number of bytes allocated by the process that cannot be shared with other processes. This counter is primarily used to determine whether a process has a memory leak during performance testing. For example, for a Web application on top of IIS, we can focus on monitoring the private Bytes of the Inetinfo process.

If the private Bytes counter value of the process is increasing during the performance test, or a period after the performance test is stopped, the private bytes of the process continues at a high level, indicating that the application has a memory leak.

5. Network Analysis method

(1) The network interface:bytes total/sec is the rate at which bytes are sent and received, which can be used to determine if the speed of the link is a bottleneck, by comparing the value of the counter with the current bandwidth of the network.

(2) analysis in combination with processor:privileged time

If the physical disk counter, only%disk time is large, the other values are relatively moderate, the hard disk may be a bottleneck. If a few values are large and the values continue to exceed 80%, a memory leak can occur.

Windows Performance Monitor