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.
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.
R5 shared database script
Shared database script samples are as follows.

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.
    - 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.
      - Server.Load script conventions
        Review the following sample script and the breakdown of its elements to understand the conventions of the Server.Load command language. This sample script example creates and initializes mail file(s).
      - Using the sample Server.Load scripts
        Many of these scripts were created using a specific template that may change from release to release, so take this into consideration when using or customizing any of these scripts.
      - Idle Workload script
        You can use this script for the Idle Workload test.
      - SMTP and POP3 Workload script
        You can use SMTP and POP3 Workload scripts.
      - Web Idle Workload script
        You can use this script for the Web Idle Workload test.
      - Web Mail Workload script
        You can use this script for the Web Mail Initialization Workload test.
      - R5 IMAP workload script
        Various IMAP workload scripts are as follows.
      - R5 Simple mail routing script
        Various mail routing scripts are as follows.
      - R5 shared database script
        Shared database script samples are as follows.
      - Sametime® 7.0 workload script
        The Sametime® 7.0 Initialization workload script is also called the ST70Init workload script.
      - Sametime® 7.0 Instant Messaging workload script
        You can use this script to test the Sametime® Instant messaging workload.
      - Sametime® 7.5 Instant Messaging workload script
        The Sametime® 7.5 Instant Messaging workload script is as follows.
    - 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

R5 shared database script

Shared database script samples are as follows.

Shared database script sample

Text enclosed in asterisks (**) indicates comments.

**Pause a random interval so multiple processes are staggered well. Pause 0-5 minutes (5 min. = 300000 ms)**

Pause 0-300000

**If an error occurs, wait 1-2 minutes before retrying.**

ErrorDelay 60000-120000

BeginCrit

**Create a discussion database**

changeto "[MailServer]!![DiscussionDB]" [DiscTemplate] -KeepOpen

open

**Reset initial document count by deleting a large value of existing documents**

getall

@If [NBTestReset]

delete [MaxDocToDelete]

@EndIf

**Make sure there are enough documents in mail database (one time only)**

populate [NumMailNotesPerUser]

close

**Open the current view**

Open

**Close the view**

1close

EndCrit

**Start the part of the script which loops**

BeginLoop

**Open a discussion database**

changeto "[Mailserver]!![DiscussionDB]" [DiscTemplate] -KeepOpen

**Open the current view**

open

getall

**Read 20 documents from current view**

entries 1 20

**Wait 5-10 seconds to peruse the view**

Pause 5000-10000

**Page down the view 2 times, spending 3-10 seconds to read each window**

entries 21 20

pause 3000 - 10000

entries 41 20

pause 3000 - 10000

**Set the unread list to 30 randomly selected documents**

unread 30

**Open next 3 unread documents and read each for 10-30 seconds**

navigate 1 next_unread

pause 10000 - 30000

navigate 1 next

pause 10000 - 30000

navigate 1 next

pause 10000 - 30000

add [DiscDbAddDocRate] 100

**Delete 2 old documents when closing database**

close

**Pause at desktop 4 - 8 minutes while having meeting in office**

pause 240000 - 480000

**Repeat entire sequence over again (go back to BeginLoop statement)**

rewind