• Makale

Reading Jetstress 2010 Test Reports

 

Applies to: Exchange Server 2010 SP1, Exchange Server 2010

Topic Last Modified: 2010-12-15

After the test is completed, the performance data is analyzed and reported in a summary report. Results are saved to the Perf_(DateTime).html or Stress_(DateTime).html file. The log text pane of JetstressWin.exe provides a link to the summary report.

To see a sample test result from a performance test, see Example of a Jetstress 2010 Test Summary Report.

The following summarizes how to interpret the summary report:

  • The Test Summary legend summarizes the test run.

  • The Test Issues legend indicates whether the test passed or failed. It also indicates any performance samples averages and spikes that have exceeded thresholds.

  • The Database Sizing and Throughput legend explains your planned Exchange database sizing in addition to the input/output (I/O) throughput target.

  • The Jetstress System Parameters legend explains the parameters that relate to the Exchange database engine.

  • The Database Configuration legend lists the database files and log paths, grouped by Jetstress 2010 instance.

  • The Transactional I/0 Performance legend shows the throughput, average I/O size and latency for read and write disk operations that are related to user activity, and log replication. The numbers are grouped by Jetstress 2010 instance for both database and log operations.

  • The Background Database Maintenance I/0 Performance legend shows the database read throughput and average size for operations triggered by background database maintenance.

  • The Log I/0 Performance legend explains log read throughput and average size for operations triggered by log replication.

  • The Total I/0 Performance legend explains throughput, average I/O size and latency for read and write disk operations, taking into account all the operations triggered by Jetstress 2010.

  • The Host System Performance legend summarizes other non-I/O performance metrics. Be aware that these figures could be indirectly affected by storage performance.

  • The Test Log legend shows the test output with timestamps for the most important events.

The remainder of the summary report is logging information taken during the test. You can use that information for troubleshooting if the test isn't completed.

Consider the guidelines in the following table when you're examining the data in a Jetstress 2010 report.

Test results table

Performance counter instance Guidelines for performance test Guidelines for stress test

I/O Database Reads Average Latency (msec)

The average value should be less than 20 milliseconds (msec) (.20) and the maximum values should be less than 50 msec.

The maximum value should be less than 100 msec.

I/O Log Writes Average Latency (msec)

Log disk writes are sequential, so average write latencies should be less than 10 msec, with a maximum of no more than 50 msec.

The maximum value should not exceed 100 msec.

%Processor Time

Average should be less than 80% and the maximum should be less than 90%.

Same as for performance test.

Available Mbytes (32-bit Windows Server only)

Minimum should be no less than 50 megabytes (MB).

Same as for performance test.

Free System Page Table Entries (32-bit Windows Server only)

Minimum should be no less than 5,000.

Same as for performance test.

Transition Pages Repurposed/sec (Windows Server 2003, Windows Server 2008, Windows Server 2008 R2)

Average should be less than 100.

Same as for performance test.