Windows System performance Monitoring settings

WindowsSystem performance Monitoring settings

# # # Note: this was summed up when using Windows 2003. Today, a friend asked, a thought has been summed up, but also look at Windows Help or the query summary on the network, issued to stay as a souvenir, memories have maintained thousands of Windows 2003 years!

1 , Memory information:

Memory\ Available Bytes ,memory\ pages/sec ,memory\ Available Bytes,Available Mbytes , /c10>page/sec

( 1 memory\ Availablebytes and memory\committed bytes process\ Private bytes and Process\ Handle count memory\ Pool nonpaged bytes memory\ pool Nonpaged Allocs and Process (process_name) \ Pool nonpaged Bytes

(2)Available Mbytes: The number of physical memory available. If the value of Available Mbytes is small (4 MB or less), the total memory on the computer may be insufficient, or a program does not release memory. (this item is monitored during testing and the data collected is multiplied by 1024x768 equivalent to the task Manager --- Physical Memory --- the value of the available number ")

(3)page/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 page faults. Generally if the pages/sec continues above hundreds of, then the paging activity should be studied further. It may be necessary to increase the memory to reduce the need for paging (this number can be multiplied by 4k to get the resulting drive data traffic).

(4)% Committed Bytes in use : is between memory\\committed Bytes and memory\\commit Limit Ratio. (Committed memory refers to the in-use physical RAM that has reserved space in the paging file if it needs to be written to disk.) Commitlimit is determined by the size of the paging file. If the paging file is enlarged, the scale will decrease ). This counter displays only the current percentage; it is not an average.

2 ,CPU Information:

( 1 system\processor Queue Length : For bottleneck detection, threads are waiting to be assigned cpu length of columns queued by the resource, This length does not include threads that are occupying cpu <= number of processors +1

(2)processor\% Processor time :CPU Utilization, this counter is most commonly used to see if the processor is saturated, if the value continues to exceed 95% , it indicates that the bottleneck of the current system is CPU, you can consider adding a processor or replacing a processor with a better performance. (Reference value:<80%). the Server work queues\ Queue Length counter displays the processor bottleneck. A continuous queue Length of more than 4 indicates processor congestion may occur. (monitor this item during the test, collect it in unit time CPU Data Usage % )

3 , hard disk information:

Physical Disk\% Disk time

Physical Disk\ Avg.Disk Queue Length

For example, include Pagereads/sec and % Disk time and avg.disk queuelength. If the page read operation rate is low and the value of% Disk Time and avg.disk Queue Length is high, there may be a disk bottle diameter. However, if the queue length increases at the same time that the page read rate is not reduced, there is insufficient memory.

Please observe The value of the PROCESSOR\INTERRUPTS/SEC counter that measures the speed of service requests from input / output (I/O) devices. If the value of this counter increases significantly and system activity does not increase correspondingly, there is a hardware problem.

Physical Disk\ Disk reads/sec and Diskwrites/sec

Physical Disk\ Currentdisk Queue Length

Physical Disk\% Disk time

Logicaldisk\% Free Space

When you test disk performance, log performance data to another disk or computer so that the data does not interfere with the disk that you are testing.

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 that the disk took 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 average transfer time for higher disks is greater than 0.3 seconds.

You can also view the value of the Avg.diskbytes/transfer. A value greater than KB indicates that the disk drive generally works well, and a lower value is generated if the application is accessing the disk. For example, an application that randomly accesses a disk increases the average disk Sec/transfer time because random transfers require additional search time.

Disk Bytes/sec provides the throughput rate of the drive system.

Determining the balance of workloads

to balance the load on a network server, you need to know how busy the server disk drives are. Use the physical disk\% Disk Time counter, which displays the percentage of drive activity times. If the% Disk Time is higher (more than 90%), check the physicaldisk\ Current disk Queue Length counter to see the number of system requests that are waiting for disk access. the number of wait I/O requests should remain at 1.5 to 2 times greater than the number of spindles that comprise the physical disk .

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

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

4 , Nic

Network Interface\Bytes total/sec : Represents the rate at which data bytes are processed by the net adapter and the rate at which bytes are sent and received. This counter includes all applications, file data, and protocol information such as the packet header. (monitor this item when testing)

Note: Use the performance help to search for "system performance", you can find the relevant instructions.

###### Example :#####

(1)\\FRGY21\Memory\% Committed bytesin use

(2)\\FRGY21\Memory\Available MBytes

Note: The number of physical memory available, multiplied by the amount of data collected, is equivalent to the "Task Manager --- physical memory --- available value"

(3)\\FRGY21\Network Interface (intel[r]82574l Gigabit Network Connection 2) \bytestotal/ Sec

Note: Network card the traffic that is monitored by the LAN, in Bytes total/sec units.

(4)\\FRGY21\Network Interface (intel[r]82574l Gigabit Network Connection) \ Bytestotal/sec

Note: Network card traffic monitored by the WAN

the "100mbps/8=12.5mb/s 1mb/s=1024kb/s 1kb/s=1024b/s" is represented as:

Performance counter statistics to:1788023.377Bytes total/sec

1788023.377[Bytes total/sec(b/S)]/1024

=1746.1166 (KB/S)/1024

=1.705 (M/s) * 8

=13.64mbps

(5)\\FRGY21\Processor (_total) \%processor time

Note: Acquisition within a unit of time CPU data usage %

Need to expand:

(6) Queue Length counter

Avg.Disk Queue Length

 // The average number of read and write requests (queued in the instance interval for the selected disk)

Current Disk Queue Length

// is the current number of requests on the disk when performance data is collected. It also includes requests that are in service at the time of collection. This is a snapshot of the moment, not the average of the time interval. A multi-axis disk device can have multiple requests that are in a running state, but other concurrent requests are waiting for service. This counter reflects a temporary high or low queue length, but it is likely to remain high if the disk drive is forced to run continuously. The delay of the request is proportional to the length of this queue minus the number of spindles on the disk. To improve performance, this difference should be less than two on average.

Throughput Counters
%disk bytes/sec//measurement of transfer rate, which is an important indicator of disk throughput
%disk Read bytes/sec
%disk Write bytes/sec
Utilization Counters
%disk time
%disk Read Timeand the%disk Write time//percentage of time a disk drive is used to process read/write requests
%Idle Time// the disk system does not process the request and the percentage of time that is not requested in the queue
disk transfers/sec disk reads/sec diskwrites/sec

Split io/sec

// reports the rate at which I/O on disk is split into multiple I/O. A split I/O may be caused by the fact that the requested data is too large to fit into a single I/O or disk fragmentation.

This article is from the "Old Wafangdian" blog, please be sure to keep this source http://laowafang.blog.51cto.com/251518/1725792

Windows System performance Monitoring settings