Scaling Microsoft Exchange 2000: Create and Optimize High-Performance Exchange Messaging Systems
A hands-on guide to designing and building an Exchange-based messaging system that will grow with your enterprise.
TABLE OF CONTENTS Scaling Microsoft Exchange 2000: Create and Optimize High-Performance Exchange Messaging Systems
6.2: Exchange 2000 workload simulation
6.2 Exchange 2000 workload simulation
There are two families of tools to be used with Exchange 2000. One, directly inherited from Exchange 5.5, is Microsoft LoadSim. LoadSim aims at testing and generating load for MAPI clients only. Given the emphasis of Exchange 2000 on Internet protocols, ESP, a beefed-up version of InetLoad was created (code-named Medusa) and was used to generate load and measure response time for Internet protocols (e.g., POP, IMAP, and HTTP).
For individual directory load simulation, you can use LoadSim, which will simulate directory lookups via MAPI (it will also exercise the DS_PROXY component of the Exchange 2000 server), or ADTest, a specific tool that will generate and measure response time for concurrent LDAP calls to an Active Directory controller (GC or DC).
6.2.1 LoadSim 2000
LoadSim was developed early along with Exchange 4.0; it provides a solid tool and a de facto industry standard for simulating MAPI connections on an Exchange 2000 server. LoadSim must be carefully used, because it can produce misleading results. For example, if your load simulation clients are overloaded (!), they won't simulate as many users as you might assume.
LoadSim consists of an environment composed of several components:
-
Sy stem under test (SUT) This is the system you wish to apply the load on and possibly measure the response time of (known as the score) as well as its behavior under activity.
-
Load clients Typically, you will use between 500 and 600 MAPI connections per loading client. Thus,...
Copyright Butterworth-Heinemann 2002 under license agreement with Books24x7
