PERFORMANCE


R6 Mail Routing workload
The R6Mail Routing workload models an active user on a client reading and sending mail, using the calendar and scheduling features to schedule an appointment, send an invitation, and send an RSVP to an invitation. An average user will run this script four times per hour. Each script iteration reads five documents, updates two documents, deletes two documents, scrolls a view once, opens and closes one database, opens and closes one view, sends one memo to three recipients, and does three lookups on the IBM® Lotus® Domino® Directory (when NthIteration=6). Every 90 minutes, the test schedules one appointment and sends one invitation to the recipients. There are server name lookups, and messages are deposited in the SUT mailbox.

Metrics

This test measures:


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.

Requirements


Test Initialization

If you have not already created mail databases, do so before running the test. Use the NRPC Mail Initialization workload to create the mail files.

NOTES.INI Settings for the test driver for R6Mail

The following is an example of the NOTES.INI settings for the test driver:


NOTES.INI settings for the R6 Mail SUT
Other suggested SUT settings include:
Server document settings for the R6 Mail Routing test

Be sure that the Basics tab of the Server document uses these settings:


Running the R6 Mail Routing test

1. Make sure that you 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 R6 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:
VariableAction
MailServerEnter the canonical name of the mail server -- for example, CN=MailServer1/O=Acme.
nb_dbdirEnter a database directory relative to the Notes data directory. Recommended value is mail\.
MailTemplateEnter the name of the mail file template.
NBTestResetEnter 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.
MaxDocToDeleteEnter the number of documents to delete when the test starts. After deleting documents, the initial document count is reset.
NumMailNotesPerUserNumber of notes used to populate the mail file when the mail file is created (recommended value 100)
NormalMessageSizeEnter the size of the body of the message. Recommended value is 10000.
NumMessageRecipientsEnter the number of recipients for each message. Recommended value is 3.
NthIterationEnter 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.
NB_Mail_FT_Search_EnabledUse one of these settings:
  • 0 -- To disable full text search while the workload is running.
  • 1 -- To enable full text search while the workload is running.
ScriptIterationLimitEnter 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