NRPC Mail Initialization workload

Use the NRPC Mail Initialization workload to prepare for the R5 Simple Mail Routing workload and the R6 Mail Routing workload. The NRPC Mail Initialization workload creates the mail databases for the R5 Simple Mail Routing workload and the R6 Mail Routing workload.

Procedure

  1. Make sure that you already set up clients and servers for Server.Load.
  2. From the Domino® Administrator client, start Server.Load.
    Table 1. Variables for Server.Load

    Variable

    Setting

    Message storage format

    0 (NOTES)

    Mail system

    1 (NOTES)
  3. In the Test Type field, choose Built-In, and then choose NRPC Mail Initialization Workload from the list.
  4. Click the Test Parameters tab, and do the following:
    1. For Thread Creation Interval, enter the rate, in seconds, at which simulated users are created. The recommended value is 3 to 5 seconds.
    2. 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:
    Table 2. Script Variables tab

    Variable

    Action

    MailServer

    Enter the canonical name of the mail server -- for example, CN=MailServer1/O=Renovations.

    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.

    NumMailNotesPerUser

    Number of notes used to populate the mail file when the mail file is created (recommended value is 100)

    NormalMessageSize

    Enter the size of the body of the message. Recommended value is 10000.
  6. In the Build Recipient List using Name and Address Book field, enter the name of the SUT and its Domino Directory in the format servername/org!!dominodirectory.NSF -- for example, Server1/Renovations!!NAMES.NSF.
  7. Verify that no errors occur while creating mail files on the client and SUT. If a mail file is not created, the test script creates the mail file during the first test iteration, a process that adds overhead on the server back end. As a rule, CPU on the client and SUT should not exceed 75%, and the percentage of disk time on the server's data directory should not be a factor.
  8. Optional: Click the Stop Conditions tab to set a stop condition.
  9. Click Execute.
  10. Optional: Select metrics to monitor.
  11. Optional: In the Server to receive console commands field, enter the name of the SUT.
  12. Click Start Test.
  13. Verify that the correct number of test mail files were created in the data directory. Each mail file is named MAILn.NSF, where n is a number.
  14. Complete the procedure to run the R5 Simple Mail Routing workload or the R6 Mail Routing workload.