Performance Monitoring and Context Switches

In deze post plaats ik een aantal links over performance monitoring en context switches.

Microsoft

• http://www.microsoft.com/technet/
• http://technet2.microsoft.com/
• http://www.microsoft.com/technet/

Citrix

• http://support.citrix.com/article/CTX115001

Overige sites

• http://www.thomaskoetzing.de/
• http://www.windowsnetworking.com/
• http://softwarecommunity.intel.com/

De volgende quote komt uit het document van de Intel site.

Counter (Parent Object)
Recommended Range

% CPU Time (System)
0-90% ( > 90% indicates potential processor bottleneck; may also indicate thread contention problem; investigate Context Switches/sec and System Calls/sec for potential thread issues)

% Privileged Time (System)
0-40% ( > 40% indicates excessive system activity; correlate with System Calls/sec)

Context Switches/sec (System)
0-10,000 ( > 10,000 may indicate too many threads contending for resources; correlate with System Calls/sec and threads counter in Windows Task Manager to identify process responsible)

File Control Operations/sec (System)
Ratio dependent (The combined rate of file system operations that are neither reads nor writes [file control/manipulation only, non-data related]. Inverse of File Data Operations/sec)

File Data Operations/sec (System)
Ratio dependent (Combined rate of all read/write operations for all logical drives. Inverse of File Control Operations/sec)

System Calls/sec (System)
0-20,000 ( > 20,000 indicates potentially excessive Windows system activity; correlate with Context Switches/sec and threads counter in Windows Task Manager to identify process responsible)

Interrupts/sec (System)
0-5000 (> 5000 indicates possible excessive hardware interrupts; justification is dependent on device activity)

Pages/sec (Memory)
0-200 ( > 200 warrants investigation into memory subsystem; define reads (pages in) versus writes (pages out); check for proper paging file and resident disk configuration; May indicate application memory allocation problems, heap management issues)

Average Disk Queue Length (Logical Disk)
0-2 ( > 2 indicates potential disk I/O bottleneck due to I/O subsystem request queue growing; correlate with Average Disk sec/Transfer)

Average Disk sec/Transfer (Logical Disk)
0-.020 ( > .020 seconds indicates excessive request transfer latency and potential disk I/O bottleneck; define reads/sec versus writes/sec; correlate with Average Disk Queue Length)

Bytes Total/sec (Network Interface)
Depends upon interface type (10baseT, 100baseT) A potential network I/O bottleneck exists when throughput approaches theoretical maximum for interface type. (For example, 10baseT theoretical maximum = 10 x 1,000,000 bits = 100 Mbits/sec divided by 8 = 12.5 Mbytes/sec)

Packets/sec (Network Interface)
Depends upon interface type (10baseT, 100baseT)