Configuration and Performance

Overloading the server obj.conf with too many assign-name directives can have an adverse effect on performance. Each assign-name directive involves a regular expression comparison which can prove CPU intensive.

The following tables contains the performance results with varying number of assign-name directives in the server obj.conf.

The first set of data is for a server with cache enabled, and the content server present in the local network. Note that the response time is for a single request.

As can be seen from the performance numbers, the response times show a marked increase once the number of assign-name directives cross 100.

The following data was obtained with the cache disabled, and the remote server residing in a remote network.

In the above data, a combination of network delay and the absence of a disk cache tend to hide any performance drop due to the computational delay caused by the high number of assign-name directives.

Recommendations:

• Do not let the assign-name directives run into hundreds

• Those assign-name directives that match commonly accessed URLs should appear earlier in the obj.conf