IBM System Verification Test for
Windows 2003 (64 bit) with Domino 8.5.1
The IBM System Verification Test (SVT) objective is to execute a set of test scenarios against a test configuration that contains the key requirements and components that will create a load on an Windows 2003 64 bit machine.
This testing used test scripts currently used by the Domino System Test team.
One's perception of system quality is governed under the statement of overall system reliability. A widely accepted definition of software reliability is the probability that a computer system performs its destined purpose without failure over a specified time period within a particular execution environment. This execution environment is known formally as the operational profile, which is defined in terms of sets of possible input values together with their probabilities of occurrence. An operational profile is used to drive a portion of the system testing. Software reliability modeling is therefore applied to data gathered during this phase of testing and then used to predict subsequent failure behavior during actual system operations
A reliability test is one that focuses on the extent to which the feature or system will provide the intended function without failing. The goal of all types of testing is the improvement of the reliability program with specific statements about reliability-specific tests. Reliability is the impact of failures, malfunctions, errors and other defect related problems encountered by customers. Reliability is a measure of the continuous delivery of the correct service (and, the time to failure).
SVT's purpose of running Reliability tests was to ascertain the following:
- Data population for all parts of the infrastructure to force set limits to be achieved and passed
- Running sustained reliability scripts at >100% maximum capacity. Assessing :
- System stability pre and post breakpoint
- Forcing spikes and anti-spikes in usage patterns
- Exposing SMTP, IMAP, POP3 services to 110% of their maximum load
- Flushing out the DB Table spaces to their maximum, proving the maximum, proving ability to recover/get back to a good place when the maximum limits have been exceeded
- Proving serviceability errors and warnings when thresholds are hit
2 Configuration diagram for Windows x64 configuration
The W64 2003 configuration the domino system test team used, utilized two W64 2003 SP2 Enterprise machines, running one Domino 8.5.1 server each.
The environment consists of two W64 2003 machines with a single Domino partition running on each server. Each server host 2,000 registered users and run a number of active users, dependant on the load being applied.
It is generally recommended to use separate file system for Transaction Logging.
The design task was run prior to the start of the test to upgrade the templates. The update task runs for the entire period of the test (until the server is brought down).
Details of System under Test (SUT)
Xeon CPU 3.4GHz, 4 CPU’s
Model of Machine
IBM xSeries 3650
Local drives, per server
OS (C:) 136Gb
NotesData (D:) 136Gb
Trans (E:) 136Gb
Swap (F:) 136Gb
Mailfiles on DS6800 SAN: 500 Gb per
W64 2003 SP2 Enterprise
Domino 8.5.1 Production Build for Windows 64 bit
Table 1 shows the resources available in the physical environment
2.1 Evaluation Criteria
The performance of Domino 8.5.1 is evaluated under the following criteria:
· Server CPU: The overall CPU of the server will be monitored over the course of the experiment. The aim is for the server CPU not to go above 75% over the course of the experiment allowing the server to function appropriately. It is acceptable for the CPU to occasionally spike at this level for a short period of time, but it must return to a lower level. High CPU results from the server being stressed due to processes running such as compact, fixup or replication or from user load or any other third party programs.
· Domino Processes CPU: The previous metric monitors the overall CPU of the server, however, the CPU consumption of Domino specific processes will also be monitored individually. In this manner the CPU consumption of Domino specific processes may be evaluated.
· Server Memory: The server memory metric represents the amount of physical memory available on the server. If the available memory becomes low the server performance could be compromised.
· Server Disk I/O: The disk is a source of contention when a server is under load and performing a high number of read and write operations. The disk queue length is measured to determine if the disk I/O operations are resulting in a bottleneck for the system performance.
· Network I/O: These metrics monitor the network utilization to ensure the bandwidth consumption is acceptable and that the network is not overloaded.
· Response Times from the End-user Perspective: The server response times for user actions represent how long a single user must wait for a given transaction to complete. This metric captures the user experience of the application with the server. At times, response times will be longer when a server is under load. When response times increase over an extended period, or persist at high levels (e.g. when a database or view takes longer than 30 seconds to open), they indicate that performance indicators are being hit and detailed analysis must be performed to determine the source of the slowdown and seek remediation.
· Open Session Response Times: In addition to monitoring the individual action response times, the Open session response times will also be evaluated in order to ensure the server remains responsive over the course of the experiment.
In order to simulate user activity and capture the evaluation metrics discussed in section 2.1 a number of tools must be used:
The Server.Load is a capacity-planning tool that is used to run tests against a targeted Domino server to measure server capacity and response metrics.
· Domino showstats
data: The Domino showstats captures important server metrics. A Testnsf client driver may be used to execute the showstats console command at regular intervals for each server in the configuration and will provide Domino-specific data. The resulting data is logged in a text file and may be graphed for analysis.
· Open session
: The Open session tool measures mail file request/response times. It will open a view of a mail database at a set time interval and record the response time in milliseconds. As a result, a server slow down may be identified by analyzing the resulting response times.
· NMON Collection Services
: This is used to graph the CPU Usage, Disk IOP Utilization and Lan Utilization during the 7 day run.
2.3 Evaluation Process
The server.load tools were used to place load on the Domino server. In order to simulate realistic load on the Domino server a total of 4 client drivers running server.load were used.
Within the different test cycles, different loads were applied to the configuration. During each cycle 2000 mail users were directed at each server.
The 8.5 Mail script, while running for 24 hours over a seven day period, will start ramp up around 8.00 AM and will ramp down around 6.00 PM. The ramp up and ramp down periods will be of about one hour. This replicates a real scenario within a company. All of the web based scripts will run for 24 hours a day for a seven day period
In order to isolate the performance of the Domino server under load from a single user perspective for standard Notes mail, a client driver will execute a “single user” server.load script.
The results represent a single user experience of how the application will perform at busy times of the day when the server is heavily loaded.
Mailfiles and Domino data are stored on SAN Storage for these tests.
2.4 Scenario: Online Mode
The scenario evaluates the performance of Lotus Notes Clients in online mode. Online mode means that the user mail files are stored and maintained on the Domino server. Every time a user performs an action the request is sent to the server and the mail file is modified and updated on the server side.
N85Mail Script with attachment size modification
Action Count per hour per user current script
Action Count per 24 hour per user current script
Reply to all
Send Message to one recipient
Send Message to three recipient
Move to folder
New Mail poll
Delete two documents
Total Messages sent
Table 2 shows the action workload of the built in N85Mail script with modifications to the attachment size. The script reflects the workload that is expected of a single user over the course of a day.
Message Distribution in N85 Mail Script
Message size distribution
Percent of messages sent
Attachment size ( if any )
0 < size <= 1k
1k < size <= 10k
10k < size <= 100k
100k < size <= 1mb
1mb < size <= 10mb
The resulting mail distribution is shown in table 3.
3 Test drivers
The workload is generated by 8 “driver” workstations:
Driver9 is used for a Lotus Notes Administration client and for running statistics collection and monitoring delays in opening databases routinely on each Domino partitioned server.
4 Conclusion and Summary
The test results demonstrate that the Windows 2003 64 bit machine configured as described in this report was able to support up to 1000 concurrent, active Notes 8.5.1 users per Domino Server with an average response time below 2 seconds.
The addition of other application workloads will affect the number of users supported as well as the response time.
Achieving optimum performance in a customer environment is highly dependent upon selecting adequate processor power, memory and disk storage as well as balancing the configuration of that hardware and appropriately tuning the operating system and Domino software.
5 Configuration settings
The following notes.ini variable was added to each of the Domino Servers:
DAOSDeferredDeleteInterval=30 (This deletion of NLO files is known as “pruning” and occurs at the specified “Deferred Deletion Interval.”)
(DAOS base path, if you leave it DAOS, and your data directory is C:\Lotus\Domino\Data, the full path to the repository would be C:\Lotus\Domino\Data\DAOS)
(the minimum size setting for an attachment to make use of DAOS is 1096 bytes.)
(DAOS Catalog version to be set 3)
(state of the DAOS catalog)
(to enable ODS 51 as the default)
(to enable the creation of Transaction Logs in 85 format)