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.
About this task
The measurements obtained by this test are:
- Throughput of completed Notes® operations
- Number of maximum users supported
- Average response time at maximum capacity
Note: You can review the R5 Shared Database script.
Table 1. Settings for script
Setting |
Value |
Initial disk requirement |
300MB to 400MB free space on the SUT |
Subsequent disk requirement |
One-half of the mail test space requirement |
Procedure
- Make sure that you already set up clients and servers for
Server.Load.
- From the Domino® Administrator
client, start Server.Load.
- In the Test Type field, choose Built-In, and then choose
R5 Shared Database test from the list.
- 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.
- Click the Script Variables tab, and enter these values:
Table 2. Script Variables
Variable |
Action |
MailServer |
Enter the canonical name of the mail server
-- for example, CN=MailServer1/O=Renovations |
DiscussionDB |
Enter the name of the test discussion database |
DiscTemplate |
Enter the name of the template used for the
discussion database |
NBTestReset |
Enter 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. |
MaxDocToDelete |
Enter the number of documents to delete when
the test starts. After deleting documents, the initial document count
is reset. |
NumMailNotesPerUser |
Enter the number of documents to create for
each user to populate the database initially. |
DiscDbAddDocRate |
Enter the number of documents to add for each
user. |
- Optional: Click the Stop Conditions tab to
set a stop condition.
- Click Execute.
- Optional: Select metrics to monitor.
- Optional: In the Server to receive
console commands field, enter the name of the SUT.
- Click Start Test.