Home
IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
Tuning
Use this information to improve IBM® Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
The Server.Load tool
Server.Load is a capacity-planning tool that you use to run tests, also called "scripts" and "workloads," against a targeted Domino® server to measure server capacity and response metrics.
Built-in and custom Server.Load scripts
Server.Load includes a set of built-in scripts. You can also create a custom script from scratch.
Server.Load test parameters
Before you run a Server.Load test, you can modify any of these parameters, which are located on the Test Parameters tab.

IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
- What's new in IBM® Domino® 10?
  Learn about all of the new features for administrators in IBM® Domino® 10.
- Overview
  Welcome to IBM® Domino® Administrator Help.
- Installing
  Use this documentation to install the IBM® Domino® server and subsequently deploy the IBM Notes® client.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
- Securing
  This section describes IBM® Domino® security features, including execution control lists, IDs, and SSL.
- Administering
  This documentation provides information about the administration tools for managing and monitoring IBM Domino® servers and databases.
- Tuning
  Use this information to improve IBM® Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
  - Resource balancing and activity trends
    Domino® server resource utilization can be separated into two types, system activity and user activity. System activity, which includes the level of processor, disk, memory, and network consumption that Domino generates to keep the server running, is a fixed amount of activity, as long as systems are healthy and performing smoothly. Domino servers typically use a modest percentage of their resources to run. The remaining server capacity is used to support user activity, which varies with the usefulness of the data on the server.
  - The Server.Load tool
    Server.Load is a capacity-planning tool that you use to run tests, also called "scripts" and "workloads," against a targeted Domino® server to measure server capacity and response metrics.
    - Server.Load agents
      Server.Load includes a set of agents in the file NAMAGENT.NSF, which is initially installed in the data directory on the Domino® Administrator client. The first agent in this list -- Create NotesBench Mail Person Documents -- is used to set up Person documents for the workloads and set the HTTP password. The rest of the agents are used to repair and change the workload setup.
    - Server.Load metrics and messaging statistics
      As you run a test, you can view various script metrics and server statistic metrics and optionally store the test output in a separate file. Server statistic metrics are generated by the Domino® server. Script metrics correspond to Server.Load command names and display the performance of particular commands. For example, if you select the Add metric, the Metrics window displays the results of the Add command.
    - Setting up clients and servers for Server.Load
      To use Server.Load, install the Domino® server on the server under test (SUT) and install the Domino Administration client and the Server Load Utility on each client.
    - Built-in and custom Server.Load scripts
      Server.Load includes a set of built-in scripts. You can also create a custom script from scratch.
      - Tips for running a Server.Load test
        Keep the following considerations in mind when you run a Server.Load test.
      - Server.Load test parameters
        Before you run a Server.Load test, you can modify any of these parameters, which are located on the Test Parameters tab.
      - Running a custom Server.Load script
        If you create a custom script, use these steps to run it.
      - Modifying a built-in Server.Load script
        Rather than build a script from scratch, modify a copy of a built-in script. For example, to test replication, you can edit the R5 Simple Mail Routing script to include the Replicate command.
      - Saving Server.Load settings
        If you run a workload more than once, and you often use the same settings when running the workload, use the Save Settings option on the Server.Load File menu to save the settings that you want to reuse.
      - Testing a Server.Load command
        Using the Command Line Screen, you can test an individual Server.Load command. The results of each command appear in an output window.
      - Changing a Server.Load script variable
        To further refine a test, you can change the default values of script variables.
      - Setting a Server.Load stop condition
        You can control what happens if the SUT fails to respond appropriately during a test.
    - Running the built-in Server.Load workloads
      Server.Load contains numerous built-in workloads and initialization workloads.
    - Server.Load commands
      Server.Load scripts consist of statements in a simple command language, the Server.Load specification language.
    - Server.Load scripts
      You can use any of the sample Server.Load scripts as they are or you can use them as a basis for creating customized scripts.
    - How Server.Load determines the range of mail addresses it uses when sending messages
      Server.Load uses the logic described in this topic when determining the range of mailing address to be used.
  - Tuning Domain Indexer performance
    Each time the Domain Indexer task runs, it looks in the Domain Catalog for new databases that have the Include in multi database indexing property enabled. It then looks for documents and files in existing databases and file systems that are new or changed since the last time it ran, and adds them to the Domain Index.
  - Improving Domino® server performance
    Read the following topics for help on improving basic Domino® server performance and capacity, as well as the performance of these features: Agent Manager, databases and the Domino directory, the directory catalog, LDAP searches, mail, Web server, and UNIX™ server.
  - Improving Web server performance
    After you set up the Domino® Web server and make sure that it runs properly, check the server's performance and response time.
  - Improving mail performance
    Domino® includes features that improve efficiency in specific environments, but these features may not be switched on by default.
  - Setting advanced database properties
    Advanced database properties include performance optimization and compression features, as well as ways to manage usability features such as unread marks and soft deletions.
  - Understanding cluster statistics
    Three categories of Domino® cluster statistics help you analyze clusters
  - Improving the performance of the Server Health Monitor
    If the Domino® Administration client workstation performs at 100 percent CPU utilization for a long period of time, the Server Health Monitor discards server statistic data to keep up with the workload.
- Troubleshooting
  This section describes how to find and solve problems with IBM® Domino® server and Administrator client.
- Glossary

Server.Load test parameters

Before you run a Server.Load test, you can modify any of these parameters, which are located on the Test Parameters tab.

Table 1. Test Parameters
Field	Action
Max No. of Users	Enter the number of simulated users. Default is 1. Maximum value for this setting is 1500. Note: To verify that a script is running properly, run the test the first time with only one simulated user. If you are running the test on multiple clients, increment the value of the Max No. of Users parameter when you run the test on each client. The client should not run at anything higher than 75% to 85% CPU. If the client is running at 100%, reduce the number of users.
Script Loop Count	Enter the number of times the script runs per simulated user. Default is 1. To calculate total iterations, multiply Script Loop Count by Max. No. of Users. Note: For long-duration tests, enter a large value, and specify No Time Limit in the Test Time Parameter field. If a test uses the ScriptIterationLimit script variable, set both the variable and the Script Loop Count to the same value.
Thread Creation Interval (sec)	Enter the rate, in seconds, at which simulated users are created. Default is 1 To calculate total ramp-up time, multiply Thread Creation Interval by Max. No. of Users.
Starting Thread No.	Enter the thread number that will start the test. Default is 1. Note: If you use multiple clients in a test, you must stagger the starting thread number -- for example, client 1 starts at thread 1; client 2 starts at thread 101, and so on.
Test Time Parameter	Choose one: No time limit (default) -- To run the test indefinitely. Run between two time periods -- To run the test between Start and Stop times that you enter in standard format (1:00 PM) or military format (13:00). Specify Total Test Time -- To run the test for a specific number of minutes.
Build Recipient List using Name and Address Book	Click Browse and select the Domino® Directory or Contacts file to use when building a list of recipients of the test results.
Storage test output to	Click Browse to choose the location to store test output.