PERFORMANCE


R5 Shared Database workload
The R5 Shared Database workload models active users performing shared database operations that include performing view operations, navigating unread documents, reading documents, and adding or updating documents in a shared database.

Metrics

The measurements obtained by this test are:


Note You can review the R5 Shared Database script.

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 requirement300MB to 400MB free space on the SUT
Subsequent disk requirementOne-half of the mail test space requirement

Running the R5 Shared Database test

1. Make sure that you already set up clients and servers for Server.Load.

2. On the IBM® Lotus® Domino® Administrator client, start Server.Load.

3. In the Test Type field, choose Built-In, and then choose R5 Shared Database 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
DiscussionDBEnter the name of the test discussion database
DiscTemplateEnter the name of the template used for the discussion database
NBTestResetEnter one 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.
NumMailNotesPerUserEnter the number of documents to create for each user to populate the database initially.
DiscDbAddDocRateEnter the number of documents to add for each user.
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