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.
Improving mail performance
Domino® includes features that improve efficiency in specific environments, but these features may not be switched on by default.
Changing the logging level for mail
By default, when the Router is unable to deliver a mail message, Domino® records information in the server log file (LOG.NSF). When you troubleshoot messaging, you may want to record additional information in the log file.

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.
- 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.
  - Creating multiple MAIL.BOX databases
    Domino® mail servers use a MAIL.BOX database to hold messages that are in transit. Mail clients and other servers use SMTP or Notes® routing protocols to deposit messages into MAIL.BOX. The Router on each server checks the address of each message in MAIL.BOX and either delivers the message to a local mail file or transfers it to the MAIL.BOX database on another server.
  - Determining how many MAIL.BOX databases to place on a server
    When a server sends and receives mail, server processes, such as the Router, access the server's MAIL.BOX database, writing messages to it and reading messages from it. Because only one process at a time can access MAIL.BOX, when mail traffic is heavy, access conflicts occur as multiple processes try to access the database simultaneously.
  - Disabling type-ahead addressing
    Type-ahead addressing displays names that match the letters a user types in the To, cc, and bcc fields in a mail message. For example, if a user types Jane D in the To field of a mail memo and Domino® finds a Person document for Jane Doe/Acme in the Domino Directory, Domino automatically completes the rest of the recipient's address. The user can change or retype the address as needed.
  - Changing the logging level for mail
    By default, when the Router is unable to deliver a mail message, Domino® records information in the server log file (LOG.NSF). When you troubleshoot messaging, you may want to record additional information in the log file.
- 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.

Changing the logging level for mail

By default, when the Router is unable to deliver a mail message, Domino® records information in the server log file (LOG.NSF). When you troubleshoot messaging, you may want to record additional information in the log file.

Procedure

Make sure you already have a Configuration Settings document for the server(s) to be configured.
From the Domino® Administrator, click the Configuration tab and expand the Messaging section.
Click Configurations.
Select the Configuration Settings document for the mail server or servers you want to administer, and click Edit Configuration.
Click the Router/SMTP > Advanced > Controls tab.

Complete this field in the Miscellaneous Controls section, and then click Save & Close:

Table 1. Logging level
Field	Enter
Logging level	Choose one: Minimal - Domino® logs all mandatory status messages and fatal error messages. Normal (default) - Domino® logs all minimal events, plus warning messages indicating conditions that do not cause processing to stop. Informational - Domino® logs all minimal and normal events, plus informational messages involving intermediate storage, MAIL.BOX access, message handling, message conversion, and transport status. Verbose - Domino® logs all minimal, normal, and informational events, plus additional messages that may help you troubleshoot system problems. Note: To prevent the log file from becoming excessively large, use Verbose logging only when troubleshooting specific problems.

The change takes affect after the next Router configuration update. To put the new setting into effect immediately, reload the routing configuration.