JetStress (WR2.1) has updated performance counter thresholds.

  • Articolo

Performance counter thresholds are updated. But, there are some differences from Exchange 2003 Performance Troubleshooting Guide for some reasons.

Database Disks:

  • Average Disk sec/Read (or I/O Database Reads Average Latency): The average should be below 20 ms. Spikes (maximum values) should not be higher than 50 ms.

Transactional Log Disks:

  • Average Disk sec/Read (or I/O Log Reads Average Latency): The average should be below 20 ms. Spikes (maximum values) should not be higher than 50 ms.
  • Average Disk sec/Write (or I/O Log Writes Average Latency): The average should be below 10 ms. Spikes (maximum values) should not be higher than 50 ms.

Here are the latest performance counter thresholds: 

Memory & Processor Thresholds Performance/Stress
% Processor Time (maximum) 90%
% Processor Time (average) 80%
Available Memory Bytes (minimum) 50 MB
Page Table Entries (minimum) 5000
Memory Pages Per Sec (average) 100
Pool Nonpaged Bytes (maximum) 75 MB
Pool Paged Bytes (maximum) 180 MB
Database Page Fault Stalls Per Sec (maximum) 0

Reference: Troubleshooting Exchange Server 2003 Performance 

This posting is provided "AS IS" with no warranties, and confers no rights.

Comments

  • Anonymous
    January 15, 2007
    A: There are two sets of latency thresholds defined in the Jetstress xml configuration file: One is strict