TUNING


R5 Simple Mail Routing workload
The R5 Simple Mail Routing workload models an active Notes® mail user receiving and sending mail, composing and sending meeting invitations, and scheduling appointments. The script contains an average of 15 minutes of waiting; therefore, an average user runs this test no more than four times an hour.

About this task

For each iteration of the script, five documents are read, two documents are updated, two documents are deleted, one view is opened and closed, one view-scroll is performed, one database is opened and closed, and several other operations are performed. One message is sent to each active user approximately every 96 minutes; the same frequency is used for appointments and invitations.

Because mail routing and delivery are performed on the SUT, locate the destination addresses and the active users' mail files on the SUT.

The measurements obtained by this test are:


The resulting capacity metric for a mail-only server is the maximum number of users that can be supported before the average user response time becomes unacceptable.

The following hard disk requirements apply to the SUT and, during some tests, to the destination systems that receive mail from the SUT:

Table 1. Hard disk requirements
Hard DiskRequirement
Initial Disk RequirementIn Domino® 6 or later, approximately 13MB for each user (mail database). In Domino R5, approximately 7.5MB.
Subsequent Disk RequirementIncrease of 80KB for each user, per hour.

The R5 Simple Mail Routing test requires at least one client and the SUT. If you use multiple client systems, identical hardware configurations are recommended.

Procedure

1. Make sure that you have already completed the procedure to run the NRPC Mail Initialization workload.

2. On the SUT, do the following:


3. In the Test Type field, choose Built-In, and then choose R5 Simple Mail Routing test from the list.

4. Click the Test Parameters tab. If you are running the test on multiple clients, increment the value of the Starting Thread No. parameter when you run the test on each client.

5. Click the Script Variables tab, and enter these values:


6. Optional: Click the Stop Conditions tab to set a stop condition.

7. Click Execute.

8. Optional: Select metrics to monitor.

9. Optional: In the Server to receive console commands field, enter the name of the SUT.

10. Click Start Test.

Related concepts
Running the built-in Server.Load workloads

Related tasks
NRPC Mail Initialization workload
Setting a Server.Load stop condition
Modifying a built-in Server.Load script
Tips for running a Server.Load test
Running a custom Server.Load script