Home
Tuning
Use this information to improve HCL 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.
Understanding cluster statistics
Three categories of Domino® cluster statistics help you analyze clusters
Cluster Replicator statistics
Each Domino® cluster replicator statistics name includes the prefix Replica.Cluster, which is not included in the names in this table.

Tuning
Use this information to improve HCL 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.
- Using 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.
- 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
  - Cluster Manager statistics
    Other than AvailabilityIndex, AvailabilityThreshold, and ExpansionFactor, each Domino® cluster manager statistics name includes the prefix Server.Cluster, which is not included in the names in this table. AvailabilityIndex, AvailabilityThreshold, and ExpansionFactor include the prefix Server.
  - Cluster Replicator statistics
    Each Domino® cluster replicator statistics name includes the prefix Replica.Cluster, which is not included in the names in this table.
- 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.

Cluster Replicator statistics

Each Domino® cluster replicator statistics name includes the prefix Replica.Cluster, which is not included in the names in this table.

Table 1. Statistics names
Statistic name	Description
Servers	Total servers in the cluster that are receiving replications from this server
Successful	Total successful replications since the server started
Failed	Total failed replications since the server started
Docs.Added	Total documents added by the Cluster Replicator
Docs.Updated	Total documents updated by the Cluster Replicator
Docs.Deleted	Total documents deleted by the Cluster Replicator
Files.Local	Number of databases on the current server for which there are replicas on other servers in the cluster
Files.Remote	Number of databases on other servers to which the Cluster Replicator pushes changes
Retry.Skipped	Total times the Cluster Replicator did not attempt to replicate a database. The retry is skipped when the destination server is known to be unreachable or the database is waiting for another retry attempt.
Retry.Waiting	Total number of replicas that are waiting for retry attempts
SecondsOnQueue	Total time, in seconds, that the last database replicated spent on the work queue
SecondsOnQueue.Avg	Average time, in seconds, that a database spent on the work queue
SecondsOnQueue.Max	Maximum time, in seconds, that a database spent on the work queue
SessionBytes.In	Total bytes received during cluster replication
SessionBytes.Out	Total bytes sent during cluster replication
WorkQueueDepth	Current® number of databases awaiting replication by the Cluster Replicator
WorkQueueDepth.Avg	Average work queue depth since the server started
WorkQueueDepth.Max	Maximum work queue depth since the server started