5-4 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server
OHS Virtual Host Metrics The OHS Virtual Host Metrics folder contains performance metric options for virtual
hosts, also known as access points. The following table describes the metrics in the OHS Virtual Host Metrics folder:
OHS Module Metrics The OHS Module Metrics folder contains performance metric option for modules. The
following table describes the metrics in the OHS Module Metrics folder.
5.3 Configuring Oracle HTTP Server Performance Directives
Oracle HTTP Server uses directives in httpd.conf. This configuration file specifies the maximum number of HTTP requests that can be processed simultaneously, logging
details, and certain limits and timeouts. Oracle HTTP Server supports and ships with the following three Multi-Processing Modules MPMs which are responsible for
binding to network ports on the machine, accepting requests, and dispatching children to handle the requests:
■
Worker - This is the default MPM for Oracle HTTP Server on UNIXLinux platforms. This MPM implements a hybrid multi-process multi-threaded server.
By using threads to serve requests, it is able to serve a large number of requests with fewer system resources than a process-based server. However, it retains much
of the stability of a process-based server by keeping multiple processes available, each with many threads.
■
WinNT - This is the default MPM for Oracle HTTP Server on Windows platforms. It uses a single control process which launches a single child process which in turn
creates threads to handle requests.
■
Prefork - This MPM implements a non-threaded, pre-forking server that handles requests in a manner similar to Apache 1.3. It is appropriate for sites that need to
avoid threading for compatibility with non-thread-safe libraries. It is also the best MPM for isolating each request, so that a problem with a single request will not
affect any other.
The discussion and recommendations in this section are based on the use of Worker or WinNT MPM, which uses threads. The directives listed below may not be applicable if
Element Description
Request Throughput for a Virtual Host
Number of requests per second for each virtual host Request Processing Time for
a Virtual Host Time to process each request for each virtual host
Response Data Throughput for a Virtual Host
Amount of data being sent for each virtual host Response Data Processed
for a Virtual Host Amount of data being processed for each virtual host
Element Description
Request Handling Throughput
Request handling throughput for a module, in requests per second
Request Handling Time Request handling time for a module, in seconds
Module Metrics Modules including active requests, throughput, and time for
each module
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
