Lotus Domino Administrator 8.5 Help - Sametime 7.5 Instant Messaging workload

PERFORMANCE

Sametime 7.5 Instant Messaging workload
The Sametime 7.5 IM Workload models an active Sametime user who logs in, queries policy information, queries user info, watches the locations of buddies, chats using rich text, changes status, acts on the buddy list, and logs out. The script contains an average of 15 minutes of think time so that an average user runs the distinct commands no more than four times per hour. When users first log in, they check their policy on the server, and then set their location. Next, they watch their buddy list for location changes. For each iteration of the script, the user loops through various actions. Once every three hours, the user simulates hovering the mouse over a random user which triggers a query for that user's business card based on user information. Each iteration, the user picks a random partner from the pre-populated buddy list and initiates a chat. A chat consists of sending five rich text messages consisting of HTML or an image and receiving a reply for each from the partner. Once an hour, the user sets their status to a random value and pauses, and then sets their status back to Active. Once in a six-hour period, the user adds a new buddy to their buddy list. Next, every three hours the user logs off, waits a while to simulate being busy elsewhere, and then logs back in. Once in 24 iterations, users attempt to transfer a file.

The current limitation for the workload is the total population divided into groups of "N" users and the NOTES.INI settings ST.BL.beginuser.number and ST.BL.enduser.number variables will vary accordingly on each client driver (1-1000,1001-2000, and so forth). The two NOTES.INI settings are used to maintain the internal list of available users by the ST75 workload.

Test Initialization

Run the Sametime 7.0 Initialization workload.

Metrics

The measurements obtained by this test are:

Throughput of completed IBM® Lotus® Notes® operations
Average response time at maximum capacity
Maximum number of Web Mail users supported
The number of Logins per minute
The number of Logouts per minute
The number of IM Chats per minute
The number of IM Chats missed per minute (where a partner cannot be found free to chat)
The number of IM Text based messages sent per minute
The number of IM Text based messages received per minute
The number of IM Image based messages sent per minute
The number of IM Image based messages received per minute
The number of Resolves per minute
The number of Status Changes per minute
The number of Buddy List changes per minute
The number of Awareness notifications per minute
The number of Asynchronous notifications per minute
The number of Policy Queries per minute
The number of Login Errors per minute
The number of Chat Errors per minute
The number of Buddy List Errors per minute
The number of Resolve Errors per minute
The number of File Transfers Sent per minute
The number of File Transfers Received per minute
The number of File Transfers Declined per minute
The number of File Transfer Errors per minute

ST7.5 IM Workload Functionality

Pause approximately 20 minutes
Log in users. For each user, read the buddy list from userstorage
Set user status to "Active"
Set the current user's location to a default location
Get Policy Information
Loop for script iteration limit. An average of approximately 15 minutes per loop iteration
End Loop
Pause approximately one minute
Log out

Note Testing has shown file transfer to be a resource-heavy operation; IBM recommends setting NB_DISABLEFILETRANS=1. If file transfer is required, set NB_DISABLEFILETRANS=0.

ST75IM workload think times (minutes)

For 24 Iterations: ContextIterations 1, 2, 3, 4 being 3, 24, 12, 12 respectively:

Explicit Pause Times = 192(2*4*24)

Chat Pause Times = 60(5*0.5*24 )

Status Pause Times = 80(2*5*8)

Buddy List Pause Times = 5(1*5)

Logout Pause Times = 20(1*10*2)

ST75IM workload transaction rates

For 24 Iterations (a six-hour period):

One location change and one location watch buddy list on the first login only.

Two userInfo requests for a random buddy list user.

24 chats with a user from the buddy list. Approximately five two-way messages are exchanged with a partner depending on what the NOTES.INI variables are set to, HTML vs. image count will vary.

16 status changes, one status change to Random status and then back to Active status.

One add a buddy list member to an existing buddy list group. Transaction ncludes a Resolve request and an awareness/watchlist request.

Two logouts -- will have two logins, two status changes, two policy queries.

One file transfer.

Transaction rates during a six-hour period per user:

Logins - 2

UserInfo - 16

Chats - 24

Status changes - 18

Buddy list adds - 1

Logouts - 2

Resolves - 1