Understanding Oracle HTTP Server Performance Metrics

Managing and Monitoring Server Processes 5-5 you are using the Prefork MPM. Refer to the Oracle Application Server 10g Release 3 documentation if you are using Oracle HTTP Server based on Apache 1.3 or Apache 2.2 with Prefork MPM. The Performance Directives page allows you to tune performance-related directives for Oracle HTTP Server, as illustrated in the following figure: Performance directives management consists of three areas: request configuration, connection configuration, and process configuration. You can set these configurations using the Performance Directive page of Fusion Middleware Control and by following the instructions in the following sections: ■ Using Fusion Middleware Control to Set the Request Configuration ■ Using Fusion Middleware Control to Set the Connection Configuration ■ Using Fusion Middleware Control to Set the Process Configuration

5.3.1 Using Fusion Middleware Control to Set the Request Configuration

To specify the Oracle HTTP Server request configuration using Fusion Middleware Control, do the following:

1. Select Administration from the Oracle HTTP Server menu.

2. Select Performance Directives from the Administration menu. The Performance

Directives page appears. 3. Enter the maximum number of requests in the Maximum Requests field MaxClients directive. This setting limits the number of requests that can be dealt with at one time. The default and recommended value is 150. This is for Linux only. 4. Set the maximum requests per child process in the Maximum Request per Child Process field MaxRequestPerChild directive. You can choose to have no limit, or a maximum number. If you choose to have a limit, enter the maximum number in the field. 5. Enter the request timeout value in the Request Timeout seconds field Timeout directive. This value sets the maximum time, in seconds, Oracle HTTP Server waits to receive a GET request, the amount of time between receipt of TCP packets 5-6 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server on a POST or PUT request, and the amount of time between ACKs on transmissions of TCP packets in responses.

6. Review the settings. If the settings are correct, click Apply to apply the changes. If

the settings are incorrect, or you decide to not apply the changes, click Revert to return to the original settings. 7. Restart Oracle HTTP Server. See Section 4.1.4 . The request configuration settings are saved, and shown on the Performance Directives page.

5.3.2 Using Fusion Middleware Control to Set the Connection Configuration

To specify the connection configuration using Fusion Middleware Control, do the following:

1. Select Administration from the Oracle HTTP Server menu.

2. Select Performance Directives from the Administration menu. The Performance

Directives page appears. 3. Enter the maximum connection queue length in the Maximum Connection Queue Length field ListenBacklog directive. This is the queue for pending connections. This is useful if the server is experiencing a TCP SYN overload, which causes numerous new connections to open up, but without completing the pending task. 4. Set the Multiple Requests per Connection field KeepAlive directive to indicate whether or not to allow multiple connections. If you choose to allow multiple connections, enter the number of seconds for timeout in the Allow With Connection Timeout field. The Allow With Connection Timeout value sets the number of seconds the server waits for a subsequent request before closing the connection. Once a request has been received, the specified value applies. The default is 15 seconds.

5. Review the settings. If the settings are correct, click Apply to apply the changes. If

the settings are incorrect, or you decide to not apply the changes, click Revert to return to the original settings. 6. Restart Oracle HTTP Server. See Section 4.1.4 . The connection configuration settings are saved, and shown on the Performance Directives page.

5.3.3 Using Fusion Middleware Control to Set the Process Configuration

The child process and configuration settings impact the ability of the server to process requests. You may need to modify the settings as the number of requests increase or decrease to maintain a well-performing server. For UNIX, the default number of child server processes is 2. For Microsoft Windows, the maximum number of threads to handle requests is 250. To specify the process configuration using Fusion Middleware Control, do the following:

1. Select Administration from the Oracle HTTP Server menu.

2. Select Performance Directives from the Administration menu. The Performance

Directives page appears.