Some performance testing indicators with threshold values collected on the Internet)

% Processor Time: if this value continues to exceed 95%, the bottleneck is the CPU.
Interrupts/sec
If the processor usage exceeds 90% and the % InterruptTime (Interrupt) exceeds 15%, the processor may be overloaded and interrupted.
 
 
Processor queue length
Displays the number of threads waiting for execution in the queue shared by all Web servers processors. A processor bottleneck will cause this value to last greater than 2
 
_____________________________________________________________________________________
Page Faults/sec is the error Page processed by the processor per second (including soft errors and hard errors)
If this value increases occasionally, it indicates that there were threads competing for memory. If it continues high, memory may be the bottleneck.
(How much is the value higher ??)
 
Page/sec refers to the number of pages read from or written to the disk for parsing hard Page errors
Recommended 00-20 (this value will remain high if the server does not have enough memory to handle its workload. If the value is greater than 80, a problem occurs)
 
 
Pool Nonpaged
When the number of shards is relatively fixed, PoolNonpagedBytes is relatively fixed. If the number of shards increases gradually, this value increases slowly.
 
Available mbytes
Available physical memory (unit: Mbytes)
At least 10% of the physical memory is required,
If the Available Mbytes value is small (4 MB or smaller), the total memory on the computer may be insufficient, or a program does not release the memory.
 
 
_____________________________________________________________________________________________
 
% Disk time (physicaldisk_total)
% Disk Time refers to the percentage of Time that the selected Disk drive is busy providing services for read or write requests.
If all three counters are large, the hard disk is not the bottleneck.
If only % Disk Time is large and both are moderate, the hard Disk may be a bottleneck.
 
 
Disk Reads/sec indicates the read speed of the Disk.
Disk Writes/sec indicates the write speed on this Disk.
 
The following formula is used to determine the disk bottleneck:
I/O count per disk = [read count + (4 * write count)]/disk count
If the I/O quantity calculated per disk is greater than the disk's processing capacity, the disk has a bottleneck.
 
 
Including Page Reads/sec, % Disk Time, And Avg. Disk Queue Length.
If the page reading speed is very low and the value of % Disk Time and Avg. Disk Queue Length is very high, there may be Disk bottle diameter.
However, if the length of the queue increases while the page read rate does not decrease, the memory is insufficient.
 
____________________________________________________________________________
Bytes total/sec
Bytes Total/sec is the speed at which Bytes are sent and received, including frame characters. Determine whether the network connection speed is a bottleneck. You can use the counter value to compare with the current network bandwidth.
 
The counter value is different from the current network bandwidth, and the result should be less than 50%
 
Output queue length
Display the length of the output queue. Generally, the length is 1 or 2.
 
Database :_______________________________________________________________________________
Cache Hit Ratio
The higher the value, the better. If the duration is lower than 80%, consider increasing the memory.
Note that the value of this parameter is accumulated after SQL Server is started. Therefore, after running for a period of time, this value cannot reflect the current value of the system.

This article from the CSDN blog, reproduced please indicate the source: http://blog.csdn.net/lengyue_112/archive/2006/03/30/644382.aspx