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.

Metrics

The measurements obtained by this test are:

• Throughput of completed Notes operations
• Average response time at maximum capacity
• Maximum number of mail users supported

Hardware considerations

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

Initial Disk Requirement	In IBM® Lotus® Domino® 6 or more recent, approximately 13MB for each user (mail database). In Domino R5, approximately 7.5MB.
Subsequent Disk Requirement	Increase 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.

Running the R5 Simple Mail Routing test

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

2. On the SUT, do the following:

1. Start the Calendar Connector task (Calconn).
2. In the Configuration Settings document on the Router/SMTP Basics tab, set the field "Number of mailboxes" to 2 or higher.

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:

Variable	Action
MailServer	Enter the canonical name of the mail server -- for example, CN=MailServer1/O=Acme.
nb_dbdir	Enter a database directory relative to the Notes data directory. Recommended value is mail\.
MailTemplate	Enter the name of the mail file template.
NBTestReset	Enter one of these to control how to handle existing documents at the start of the test: 1 -- To delete existing documents 0 -- To ignore existing documents Note The number of documents deleted is dependent on the value set for the variable MaxDocToDelete.
MaxDocToDelete	Enter the number of documents to delete when the test starts. After deleting documents, the initial document count is reset.
NumMailNotesPerUser	Number of notes used to populate the mail file when the mail file is created (recommended value 100)
NormalMessageSize	Enter the size of the body of the message. Recommended value is 10000.
NumMessageRecipients	Enter the number of recipients for each message. Recommended value is 3.
NthIteration	Enter the frequency for how often a message is sent. Instead of the message being sent on every script iteration, the message is sent once per n iterations of the script. Recommended value is 6.
ScriptIterationLimit	Enter the number of times the outer loop of the test script runs. Recommended value is 1. This value must match the value in the Script Loop Count field on the Test Parameters tab.

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 topics

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 the built-in Server.Load workloads
Running a custom Server.Load script

Glossary