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.
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.
Database size quotas
Set a database size quota to specify the maximum size a database can attain.

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.
  - 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.
    - Setting database properties that optimize database performance
      You can set database properties to optimize database performance and to reduce database size. Set database performance properties by opening the Database Properties box on an existing database or as you create a database.
    - Enable soft deletions
      In some databases, deleting a document permanently removes it from the database. In other databases, such as the Notes® mail file database, deleting a document moves it into a Trash folder and stores it in a state of "soft deletion." From this folder, users can restore deleted documents by selecting Restore.
    - Using database design compression
      Use the advanced database property Compress database design to reduce the total cost of ownership of maintaining any Notes® database by reducing the size of all design elements in the database.
    - Using document body compression
      Use the advanced database property Compress document data to reduce the total cost of ownership of maintaining any Notes® database by compressing non-summary item data in all documents in a selected database. Document compression can provide up to a sixty percent size saving.
    - The database cache
      To minimize delays that occur when users, servers, or API programs open and close databases on a server, each server maintains a database cache. When a database closes and there are no users or processes using the database, Domino® puts the database in the cache so it can close it quickly. The database remains in the cache until it's opened again or for about 15 to 20 minutes, whichever comes first. Databases in the cache can be opened quickly.
    - Tools for monitoring database size
      This table summarizes the methods you can use to monitor database size and the information each method provides.
    - Monitoring database size
      You can monitor size and used space in a database.
    - Compacting databases
      When documents and attachments are deleted from a database, Domino® tries to reuse the unused space, rather than immediately reduce the file size. Sometimes Domino will not be able to reuse the space or, because of fragmentation, cannot reuse the space effectively until you compact the database.
    - Determining the file format of a database
      You can check the ODS (on-disk structure) and determine the file formats of databases before compacting them.
    - Compact options
      This topic describes options you can use with the Compact server task.
    - Database size quotas
      Set a database size quota to specify the maximum size a database can attain.
      - Setting database size quotas
        You can set size quotas for a database or multiple databases. You can also see existing quota information for databases including absolute maximum size, current database size, and any existing quotas or warning thresholds.
    - Deleting inactive documents
      Regularly delete inactive documents from databases to save disk space, to make it easier for users to find information, and to improve database performance.
    - Allowing more fields in a database
      You can increase the number of fields in a database by selecting the advanced database property Allow more fields in database which allows the database to contain up to 23,000 fields.
  - 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

Database size quotas

Set a database size quota to specify the maximum size a database can attain.

When a database exceeds its quota, the following message appears in the Miscellaneous Events view of the log file (LOG.NSF): Unable to write to database -- database would exceed its disk quota. Although a database may have reached its quota, a user may be able to add documents to it if the database contains unused space -- that is, space that remains from deleted data.

In conjunction with setting a quota, you can specify that when a database reaches a certain size threshold, this warning message appears in the Miscellaneous Events view of the log file: Warning, database has exceeded its size warning threshold. For example, if the quota is 50MB, you might specify that the warning appear when the database size reaches 45MB so you can take steps to reduce the size of the database or move it to a server that has more disk space available.

Note: You can set quotas on user mail files, but, by default, when a mail file exceeds its quota, the Router continues to deliver mail to it, and users can update existing mail views. This ensures that users can continue to receive and read all mail sent to them. The quota is enforced only for other means of increasing the size of the mail file -- for example, when a mail file reaches its quota, users can't manually add documents or views to it. However, you can customize routing to strictly enforce quotas on mail files.

Databases at ODS 53 or higher can attain a maximum size of 256GB on Microsoft™ Windows™ and UNIX™. Otherwise, the maximum database size is 64GB.