Analyze performance bottlenecks based on performance Monitor

Can be in Control Panel-admin tool-performance, inside can see the following value

One, monitor memory counters
To monitor for a low memory condition, start with the following object counters:
1. Memory Information:
Memory\ Available Bytes
Memory\ pages/sec
Memory\ Available Bytes
If you suspect a memory leak, monitor the memory\available Bytes and Memory\ committed Bytes to observe the memory behavior and monitor the process\ Private Bytes of the process that you think might be leaking memory, Process\ Working Set and Process\ Handle Count.
If you suspect that the kernel-mode process is causing the leak, you should also monitor Memory\ Pool Nonpaged Bytes, memory\ Pool Nonpaged Allocs and process (process_name) \ Pool Nonpaged B Ytes.

2.CPU Information:
Processor\% Processor time for processor usage.
You can also choose to monitor processor\% User time and% Privileged time for more information.
The Server Work queues\ Queue Length counter shows the processor bottleneck. A queue length of longer than 4 indicates a possible processor congestion.
system\ Processor Queue Length for bottleneck detection
By using Process\% Processor time and process\ Working Set
Process\% Processor The total processor time on each processor for all threads in the duration process.

3. Hard Drive Information:
Physical Disk\% Disk time
Physical Disk\ Avg.Disk Queue Length
For example
1 Page reads/sec and% Disk time and Avg.Disk Queue Length. If the page read operation rate is very low and the value of% Disk Time and Avg.Disk Queue length is high, there may be a disk bottle path. However, if the queue length increases while the page read rate does not decrease, there is not enough memory.

Physical Disk\% Disk time
Physical Disk\ Avg.Disk Queue Length
For example
1 includes Page reads/sec and% Disk time and Avg.Disk Queue Length. If the page read operation rate is very low and the value of% Disk Time and Avg.Disk Queue length is high, there may be a disk bottle path. However, if the queue length increases while the page read rate does not decrease, there is not enough memory.

2 Observe the value of the Processor\ interrupts/sec counter, which measures the speed of service requests from input/output (I/O) devices. If the value of this counter is significantly increased and the system activity does not increase accordingly, there is a hardware problem.

Physical Disk\ disk reads/sec and disk writes/sec
Physical disk\ Current Disk Queue Length
Physical Disk\% Disk time

Logicaldisk\% Free Spaces

When you test disk performance, log performance data to another disk or computer so that the data does not interfere with the disk you are testing.
1 additional counters that may need to be observed include physical disk\ Avg.Disk Sec/transfer, Avg.Disk bytes/transfer, and Disk bytes/sec.
The Avg.Disk Sec/transfer counter reflects the time it took for the disk to complete the request. A higher value indicates that the disk controller has repeatedly retried the disk because of a failure. These failures increase the average disk transfer time. For most disks, the higher average disk transfer time is greater than 0.3 seconds.
2) You can also view the value of the Avg.Disk Bytes/transfer. A value greater than KB indicates that the disk drive is typically running well, and if the application is accessing the disk, a lower value is generated. For example, an application that randomly accesses a disk increases the average disk sec/transfer time, because random shipping requires increased search time.

Disk BYTES/SEC provides a throughput rate for the disks system.

3. Determine workload balance to balance the load on the network server, you need to know how busy the server disk drives are. Using the physical disk\% Disk Time counter, this counter displays the percentage of the drive activity. If% Disk time is higher (more than 90%), check the physical disk\ Current disk Queue Length counter to see the number of system requests that are waiting for disk access. The number of waiting I/O requests should be kept to no more than 1.5 to twice times the number of spindles that make up the physical disk.

Although redundant array of inexpensive disks (RAID) devices usually have multiple spindles, most disks have a spindle. The hardware RAID device appears as a physical disk in System Monitor, and a raid device created from the software appears as multiple drives (instances). You can monitor the physical Disk counters for each physical drive (instead of RAID), or you can use the _total instance to monitor data for all computer drives.

Use the current disk Queue Length and% Disk Time counters to detect bottlenecks in the disc subsystem. If the value of current disk Queue Length and% Disk Time is always high, consider upgrading a disk drive or moving some files to another disk or server.