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.
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.
Domino® Change Manager
To implement a resource-balancing plan, you use the Domino® Change Manager task, which you load on only one server, usually the Administration server, in a domain. The Domino Change Manager uses the Domino Change Control database (domchange.nsf) to manage and implement a plan.
Setting up Domino® Change Manager
To set up the Domino® Change Manager, you load the Change Manager task. Then, the first time you run the task, it creates the Domino Change Control database (DOMCHANGE.NSF). Load this task on only one server in the domain -- usually the Administration server.

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.
- 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.
  - Setting up Activity Trends
    The basic setup for Activity Trends includes these tasks:
  - Understanding how Activity Trends collects data
    Activity Logging collects data from the log file (LOG.NSF) and the Catalog task and stores it in the Activity Trends database (ACTIVITY.NSF). The Activity Trends Collector task processes this data and produces the trended data that is used in charting and resource balancing.
  - Activity Trends server and statistics profiles
    Using profiles simplifies the work of managing groups of servers and groups of statistics. In Activity Trends, you can collect servers into a server profile, and you can specify the statistics to be included in a server profile.
  - Resource balancing in Activity Trends
    Using resource balancing, you can balance selected resources, such as database transaction load and disk space, among a selected group of servers. You decide which databases are available to be relocated as part of the resource balancing. All system databases are automatically "pinned" and cannot be moved. You can pin other databases to prevent them from being moved.
  - Primary and secondary goals for resource balancing
    To balance resources, first determine your primary and secondary goals, and specify how much weight to give each of these goals. The default goals are Notes® Transactions and Disk Space, which are the defaults for Primary and Secondary goals respectively. Because transactions factors in almost all user and server activity, and disk space is typically a constrained resource, these are a good measurement on which to balance.
  - Understanding resource-balancing behavior
    When you set the resource-balancing behavior, you balance the amount of moves made during resource balancing with the amount of accuracy achieved. Accuracy is how successfully the moves were made, based on the number of moves allowed. The higher the accuracy, the more evenly resources are balanced.
  - Analyzing resource-balancing distributions
    Use any of these procedures to analyze the current and proposed distribution of user activity on specified databases.
  - Creating a proposal for balanced resources
    Based on the selections made in the Server Profile Options dialog box, you can balance resources for a server profile that you created.
  - Evaluating server activity for resource balancing
    To balance resources, evaluate the database activity for each server on which you want to balance resources. Then compare that activity to redistributed database activity that would result from balancing resources.
  - Understanding current and projected profile charts
    To determine the proposed resource distribution, view the charts of trended statistics created by Activity Trends. The Resource Balancing view on the Server - Performance tab of the Domino® Administrator displays database activity for each server. The chart on the Current Profile tab represents the current server load. The chart on the Projected Profile tab shows how the servers will be rebalanced if the proposed plan is implemented.
  - Balancing resources in Activity Trends to decommission a server
    Decommissioning a server is a special case of workload balancing in which everything outside the default pin list is moved from the server. The databases that remain, which may still account for significant activity, are either system databases or databases that are typically installed on every server, such as templates or help files. In most cases the latter group will be the same on every server, with the possible exception of unread marks.
  - Submitting a resource-balancing plan to the Domino® Change Manager
    When you decide to implement resource balancing, you submit a plan to the Domino® Change Manager.
  - Domino® Change Manager
    To implement a resource-balancing plan, you use the Domino® Change Manager task, which you load on only one server, usually the Administration server, in a domain. The Domino Change Manager uses the Domino Change Control database (domchange.nsf) to manage and implement a plan.
    - Setting up Domino® Change Manager
      To set up the Domino® Change Manager, you load the Change Manager task. Then, the first time you run the task, it creates the Domino Change Control database (DOMCHANGE.NSF). Load this task on only one server in the domain -- usually the Administration server.
    - Specifying maximum concurrent tasks for Domino® Change Manager
      There are three thread pools that control the number of concurrent tasks that the Domino® Change Manager can carry out. The combination of the number of concurrent plans and demands creates a pool from which all the demands of all the plans are run. How the size of these thread pools affects performance depends on the size of the server.
  - Using the Tell ChangeMan command at the Domino® console
    You can use the Tell ChangeMan command at the console to control the Domino® Change Manager. The following options are available. The command Tell ChangeMan is not case sensitive.
  - ACLs for the Domino® Change Control database
    There are four ACL roles created specifically for those who are working with the resource-balancing plan. However, users or groups can also have standard Domino® ACL roles, such as Author or Reader. The roles specific to resource balancing are: Change Admin, System Admin, Plan Creator, and Plan Reader.
  - Default ACL settings for the Domino® Change Control database
    When the Change Control database (DOMCHANGE.NSF) is created, these default access levels and roles are assigned.
  - Setting ACLs for mail database moves during resource balancing
    To move databases within the domain, both the LocalDomainServers group and the Change Administrator who committed the plan must have Create Replica and Create Database rights.
  - Resource-balancing plans
    The purpose of a resource-balancing plan is to move databases according to the set of criteria defined in the Server Profile Options. The plan is based on the analysis and proposal created during data exploration in Activity Trends. When a plan is first submitted to the Domino® Change Manager, the plan has draft status. By default, the person who submits the plan to the Domino Change Manager is the author and has the Plan Creator role.
  - Database move sequences
    Database move sequences are generated by Activity Trends Resource Balancing in the Domino® Administrator. To move large groups of databases that include more than 25 moves, it groups them into sets of 25 moves or more, called demand sets. A demand set can involve any grouping of commands to be executed.
  - Setting up plan documents for resource balancing
    When you create a resource-balancing plan document, you access directly or edit information in other documents in the Domino® Change Control database (DOMCHANGE.NSF). These documents support the plan and play a critical role in providing structure to the plan.
  - Working with Domino® Change Manager constraints
    When you create a plan, you can add constraints to specify when the moves will be made to affected databases. By default, no constraints are added to a plan automatically.
- 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
- 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.

Setting up Domino® Change Manager

To set up the Domino® Change Manager, you load the Change Manager task. Then, the first time you run the task, it creates the Domino® Change Control database (DOMCHANGE.NSF). Load this task on only one server in the domain -- usually the Administration server.

Procedure

Open the NOTES.INI file for the server on which the Change Manager will run.
Add the following to the ServerTasks setting:
```
runjava ChangeMan
```
Save and close the NOTES.INI file.
At the console, enter this case-sensitive command exactly as shown:
```
load runjava ChangeMan
```

What to do next

To display full help text for this task, append -? or -help to the command.