How to pester Error Reporting immediately

1. Jetstress or Load Generator would send ‘offline’ Watson reports to the admin queue — which is located at “%SystemRoot%\PCHEALTH\ERRORREP\QSignoff”— you can send them through a file transfer service on your own. 2. The customer uses eventvwr.msc to see the application event generated. 3. The customer makes a note on the bucketing parameters — P7…


Exchange Server Jetstress (08.01.0075)

Exchange Server Jetstress (08.01.0075) March 7, 2007. Verify the performance and stability of the disk subsystem before putting the Exchange server into a production environment. • 64-bit download • 32-bit download Here is a list of issues that are all fixed in this March release.

1

Jetstress: How to include your counters in performance log.

Months ago, I got a storage vender’s feedback that his job will become a lot easier if he can define additional performance counters for his storage hardware to the performance log. I decided to provide him with a convenient way to add new performance counters (but, no way to suppress existing performance counters). When you…


Jetstress 08.01.0075 has fixed a list of issues.

Here is a list of issues that are all fixed in the March release (08.01.0075 build): Exchange 2003 database engine (ese.dll ) should have 500 MB and 900 MB database cache size min and max. DataGridView: System.InvalidOperationException: This operation cannot be performed while an auto-filled column is being resized. Help: the minimum cache size would be…

7

Exchange Load Generator (08.01.0061)

 Exchange Load Generator (08.01.0061) February 9, 2007. Perform benchmarking, pre-deployment validation, and stress testing tasks that introduce various types of workloads into a test (non-production) Exchange messaging system. Simulate the delivery of multiple MAPI client messaging requests to an Exchange server. • 64-bit download • 32-bit download

1

Exchange Server Jetstress (08.01.0038)

Exchange Server Jetstress (08.01.0038) January 3, 2007. Verify the performance and stability of the disk subsystem before putting the Exchange server into a production environment. • 64-bit download • 32-bit download

3

Q: 20 ms latency is hardcoded?

A: There are two sets of latency thresholds defined in the Jetstress xml configuration file: One is strict for a test short than or equal to 6 hours. The other is lenient for a test longer than 6 hours (it is also called a stress test).   Excerped from Jetstress chm help file — Enables you…

2

Jetstress uses Exchange 2003 SP1 ESE Performance counters for NAS storage sub-system.

Jetstress enables “Use storage volumes on NAS” when you Exchange 2003 SP1 ESE binaries (of which must be later than or equal to 6.5.7104.0) Drive letters used for the storage of Exchange 2003 database and log files are not presented as physical or logical disks; instead, they are presented as drive letters associated with a network…

7

There are risks when you run JetStress where Exchange is installed.

There are two primary risks associated with running Jetstress on a machine with Exchange installed. The first has already been discussed (Jetstress could potentially delete some existing logfiles if it’s configured to use the same log drives that Exchange is using). The second is that if you use a version of Jet (ese.dll and eseperf.*)…


EVA 5000 and HP BladeSystem Performance Articles

HP Blade System and Exchange 2003 Storage Performance (updated 2006-02-13) White Paper covers the best practices for deploying Exchange 2003 server on HP BladeSystem as well as the results of performance validation tests. HP EVA 5000 and Exchange 2003 Storage Performance (updated: 2005-07-14) White Paper covers the best pratices for EVA 5000 storage subsystem in Exchange 2003…