Find memory bottlenecks using the following counter identifies a bottleneck memory resource:
System / Processor Queue Length Memory / Pages / Sec
Find disk bottlenecks
Use the following counter to identify a bottleneck's disk resource:
PhysicalDisk /% Disk Time and% IDLE Time PhysicalDisk / Disk Reads / Sec and Disk Writes / Sec PhysicalDisk / Avg.disk Queue length LogicalDisk /% Free Space
Also monitors the memory counter to determine if there are too many memory pagings to make the disk used tensions.
Find processor bottleneck
Use the following counter to identify the processor resources of the bottleneck:
Processor / Interrupts / Sec Processor /% Processor Time Process /% Processor Time System / Processor Queue Length
Find network bottlenecks
Use the following counter to identify the network resources of the bottleneck:
Network Interface / Bytes Total / sec, Bytes Sent / sec and Bytes Received / sec Protocol_layer_object / Segments Received / sec, Segments Sent / sec, Frames Sent / sec and Frames Received / sec for NWLink performance objects, and frame-related counters only report zero. Use the object-based counter. Server / Bytes Total / Sec, Bytes Received / Sec and Bytes Sent / Sec.com Segment /% Network Utilization
Find printer bottleneck
Use the following counter to identify the bottleneck printer resources:
Print Queue / Bytes Printed / Sec Print Queue / Job Errors
The value of the printed word BYTES Printed / sec may indicate that there is a printer throughput problem. Note that this value varies depending on the type of the printer. For a value accepted by the printer throughput, see the documentation of the printer.
Job errors are generally caused by incorrect port configuration. Check if there is an invalid setting in the port configuration.
