GEPA-THE FAIR TRADE COMPANY

After installing Domino Go Webserver, you should tune the “httpd.cnf” configuration file to achieve peak performance. A properly tuned Web server significantly improves performance over the default configuration. When performance-tuning the Domino Go Webserver, you can either directly edit the configuration file or use the product configuration and administration forms. See Appendix C for the default contents of the “httpd.cnf” configuration file.

The Performance form allows an administrator to change the following values, all of which affect server performance:

Specify server priority to the operating system.
Turn off the ACL file checking.

Set a maximum number of threads.
Set persistent connection time out.

Set a maximum number of requests for a persistent connection.

The following two figures show the performance values that can be changed through the performance form.

Figure 4.4. Performance Form Persistent Connections

See the Domino Go Webserver Webmaster’s Guide for instructions on how to change server performance values.

Note The following tuning tips are not in any order of importance. Also, changes to the server configuration file require a server restart.

1. Place Frequently Referenced Files in Memory Cache

Static HyperText Markup Language (HTML) files remain constant for long periods of time. The contents can be served numerous times between updates. Static files that are frequently referenced may be cached in a server’s memory.

When the server starts, it places specified files in a memory cache. Then, when a file is requested it can be fetched from the cache, rather than from a disk. When specifying the files you want cached, you might also need to increase the default maximum bytes and maximum file limits.

Tip To increase the memory cache size for maximum bytes and files, change the values associated with the following directives:

CacheLocalMaxBytes CacheLocalMaxFiles

To load the most popular static files into the server’s memory at startup, add the file names as values associated with the following directive: CacheLocalFile

2. Suppress Time Stamp Check (for Memory Cached Files)

Each time a file in the server’s memory cache is referenced, Domino Go Webserver checks the time stamp of the file on the disk to make sure the cached copy is current. If the site content does not change frequently, suppressing the time stamp check for files in the cache can improve performance.

Tip The time stamp check suppression value is set to off by default; changing the value associated with the following directive has performance implications: LiveLocalCache off

3. Turn Access Logging Off

By default the server records that a Web browser has accessed a file in a disk log. If you do not need this access logging, turn the logging off to improve server performance.

Tip Access logging is set to off by editing the configuration file and inserting a comment character “#” at the beginning of the following directive:

AccessLog

4. Suppress Access Logging from Selected IP Addresses or Host

Names

If you do not need access logging for all requests, you can reduce the volume of data being logged and improve performance by using a log filter.

There are instances when you must log a subset of the total browser accesses. There are several methods to tell the server which accesses should not be logged.

Tip For example, to suppress logging from all browsers with IP address “9.*.*.*”, list the suppressed addresses associated with the following directive:

AccessLog Exclude

5. Turn Agent Logging Off

Tip Agent logging is set to off by editing the configuration file and inserting a comment character “#” at the beginning of the following directive:

AgentLog

6. Turn Referrer Logging Off

Tip Referrer logging is set to off by editing the configuration file and inserting a comment character “#” at the beginning of the following directive: ReferrerLog

7. Order Resource Mapping Tables

When a server begins processing a request, it searches the directives specified in the server configuration file. The server searches the “Pass” directives in the order specified within the configuration file. This search time can be reduced for specific URL sub directories by placing their corresponding “Pass” directives closer to the top of the “Pass” directives.

Tip To change the search order and improve search times for files, edit the directive statement:

Pass

Care must be taken with this approach. For example, if the very general “Pass” directive:

Pass / *

were moved to the top, then any subsequent more specific directives would be ignored.

8. Optimize Directory Listings

If you want your server to be able to return directory listings (by modifying the default “DirAccess off”), avoid some of the slower options.

Tip To return directory listings and maintain good performance, change the values with the following directives:

DirReadme off

DirShowIcons off

DirShowDate off

DirShowDescription off

9. Minimize Directory Depth

The server uses the file system when accessing a file. If the “Pass” directive being used for a particular file has a deep operating system directory structure, the file system opens and checks security (AIX read/write/execute, for example) at each level, each time the file is accessed. To reduce this processing, place the files in directories with a shallow directory structure. This will not help files that are already covered by “LiveLocalCache off,” because the file system is not consulted.

Tip To reduce the file system subdirectory searching, place files in directories that are closer to the root directory.