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.
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.
Running Web agents
You can specify whether Web application agents -- that is, agents triggered by browser clients -- can run at the same time. These include application agents invoked by the WebQueryOpen and WebQuerySave form events, and for agents invoked by the URL command OpenAgent.

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.
  - 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.
    - Managing the memory cache on the Web server
      Mapping information about databases and authenticating users can take time. To optimize response time, Domino® uses a memory cache (command cache) to store this information. The memory cache stores the information for quick access.
    - Specifying network time-outs on the Web server
      Open, inactive sessions can prevent users from accessing the server. Specify time limits for activities between the Domino® Web server and clients or CGI programs so connections do not remain open if there is no network activity between them.
    - Running Web agents
      You can specify whether Web application agents -- that is, agents triggered by browser clients -- can run at the same time. These include application agents invoked by the WebQueryOpen and WebQuerySave form events, and for agents invoked by the URL command OpenAgent.
    - Specifying the number of threads used by the Web server
      An HTTP request is processed by a thread. A thread, in turn, can handle a number of network connections. You can specify the number of threads the Web server can process. In general, the number of threads specified is an indication of the number of users who can access the server simultaneously.
    - Improving file-download performance for Web clients
      Web clients can download a file that is attached to a page or that is in a server directory that is mapped by a URL. If a client is using a product that supports byte-range serving (available in HTTP 1.1 and higher) the client downloads the file in sections -- ranges of bytes -- and tracks the progress of each file download. If an interruption occurs, the client can resume the download from the point where it was interrupted. Without byte-range serving, users must repeat interrupted downloads from the beginning.
    - Improving performance for upload of file attachments
      If large file attachments are uploaded to the Web server, out of memory conditions can result, which prevent the transaction from completing. In the worst case, low memory conditions for the HTTP task can lead to HTTP task crashes for those functions of the Domino® server that do not handle low memory conditions.
  - 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

Running Web agents

You can specify whether Web application agents -- that is, agents triggered by browser clients -- can run at the same time. These include application agents invoked by the WebQueryOpen and WebQuerySave form events, and for agents invoked by the URL command OpenAgent.

About this task

If you choose to enable this option, the agents run asynchronously. Otherwise, the server runs one agent at a time.

You should set an execution time limit for Web application agents. The purpose of the time limit is to prevent Web agents from running indefinitely and using server resources. However, do not rely on this mechanism for the routine shutdown of agents. When the server shuts down an offending agent, resources that the agent was using (such as disk files) may remain open.

Procedure

Open the Server document you want to edit.

Choose Internet Protocols - Domino® Web Engine. Under Web Agents, complete these fields:

Table 1. Web Agents fields
Field	Enter
Run Web agents concurrently?	Choose one: Enabled -- To allow more than one agent to run on the Web server at the same time (asynchronously) Disabled (default) -- To run only one agent at a time (serially)
Web agent timeout	The maximum number of seconds (elapsed clock time) for which a Web application agent is allowed to run. If you enter 0 for the value (default value), Web application agents can run indefinitely. Note: This setting has no effect on scheduled agents or other types of server or workstation agents.