Exchange Pre-Deployment Testing

JetStress (WR 1.2: 06.05.7529.0) --- Calculation is like the following: Planned Data: 750 users * 200 MB = 150 GB. Initial Data: 150 GB * 75% = 112.5 GB. Initial EDB: 112.5 GB * 1.67% = approximately 188 GB --- 112.5 GB mailbox data + 66%...

JetStress (WR2.1) uses Database Page Fault Stalls Per Sec instead of Database disk write latency. It's mainly because it could handle SRDF/sync environment. In SRDF/sync environment, database disk write latency can go over 20 ms on average, but it...

http://www.microsoft.com/technet/prodtechnol/exchange/guides/TrblshtE2k3Perf/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.mspx Exchange servers should generally have database write latencies under 20 ms, with spikes (maximum values) under 50 ms. However, it...

There are some differences between two test run types (performance and stress): Tuning phase uses different disk latency thresholds . See the JetStress documentation for the details. ( the next web release of JetStressUI will allow users to edit...

Performance counter thresholds are updated. But, t here 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...

JetStressUI ( WR2.1 ) alows multiple disk drives per storage group To reduce the initial test database creation/population time, each disk drive will host as many databases as possible. The number of databases will be decided based on the number...

JetStressUI 2004 (WR1.2: 6.5.7529.0) uses 'storage hardware cache size' for two places: One is to check the test database size is large enough and to " please make sure that the total database size is at least double the size of the storage hardward...

JetStressUI WinForm application takes Jet database operation mix, e.g. 17 inserts, 68 replaces, 5 deletes, and 90 lazy commits (those number are percentages and the rest 10% is for additionally seeking records since deletes and replaces also have seeks...