|Oracle9i Application Server Oracle HTTP Server powered by Apache Performance Guide
Release 22.214.171.124 for Windows NT
Part Number A86676-02
This chapter explains how to gather performance information from your system. This information helps you to determine the best use of your resources.
This chapter contains the following sections:
You can monitor network traffic using the Network Monitor. The Network Monitor must be installed on the Windows NT Server, and the Network Monitor Agent must be installed on the workstation (client) that is to be monitored. The Network Monitor tracks and analyzes network packets transmitted between the two computers.
For information on installing and using the Network Monitor, see the Microsoft website.
The Performance Monitor is a Windows utility that gathers performance statistics from your operating system and the Oracle HTTP Server. You can use it to:
Performance Monitor consumes a small amount of system resources; the amount depends on the frequency, size and location of the data being collected. On average, Performance Monitor uses 2-5 MB of memory and 1-5% CPU time.
The components you can monitor, such as physical disk, logical disk, and memory, are called objects in Performance Monitor. Each object has its own set of counters, performance indicators specific to the object. For example, to monitor the HTTP Server or a Java process, you would select the Process object and counters of interest, such as
% Processor Time,
% User Time,
Page Faults/sec, and
You can configure any number or combination of objects to monitor. Every system has the following objects:
To start the Performance Monitor utility:
The Performance Monitor window opens.
The Performance Monitor Chart view displays the performance counter values in real time, on a strip chart.
To create a chart of process activity:
The Add to Chart dialog box opens.
The Performance Monitor window opens with the objects and counters you selected. Figure 2-1 shows a chart view of HTTP Server (Apache) processes on two computers.
The chart view displays the performance statistics in real time, but you can enable logging to save them to a log file.
To enable logging:
The Add to Log dialog box opens.
You can view logged performance data in chart or report format. This procedure assumes that Performance Monitor is running, with a log file status of
Collecting (you have to stop the log before you can access the log file).
To create a report or chart from a log file you have saved from a prior logging session, start with Step 3.
To select data from the log file:
The display area of the window is cleared and the status changes to Closed.
The Data From dialog box appears.
The Open Input Log File dialog box opens.
The Input Log File Timeframe dialog box opens.
The data from the selected time period appears in the chart or report.
Monitoring activity on the system is essential to performance tuning. The Oracle HTTP Server provides server side status information, including current server statistics, via the
mod_status module. To obtain these server status reports, you must configure the web server as described in the following sections.
To enable monitoring, edit the httpd.conf file to replace
your_domain.com with the hostname of the computer from which you want to monitor.
Order deny, allow
Deny from all
Ensure that the
ExtendedStatus directive is set to
On, so that the maximum amount of information is displayed.
When you allow access from all domains, instead of just your_domain.com, you can monitor the server from machines outside of your domain, but be aware of the security implications of this: your server status is accessible from any site. It is probably best to specify the domain(s) from which you want to monitor your system.
With monitoring enabled, you can view current statistics from
/server-status where hostname:port is the hostname and port you want to monitor. These statistics help you to gain insight on how busy your system is.
The display includes:
Figure 2-2 is a screen capture of a server status page with
ExtendedStatus turned on.
The display (with
ExtendedStatus enabled) shows that 1 server is sending a reply.
ThreadsPerChild is set to 50, so there are 49 idle servers (the busy server is responding to the server-status request). You can determine what stage of processing each server is in from the value in the M (Mode column).
Figure 2-2 is a snapshot of a server for a moment in time. You can get updated server statistics at any interval you choose by including the refresh parameter in the server-status URL:
where servername:port is the name of the server and port number you are monitoring, and x is an integer representing the number of seconds after which the data is refreshed. For example, specify
refresh=3 to update statistics every 3 seconds.
You may also find it useful to have the statistics displayed in a machine-readable format, for processing in a data analysis or spreadsheet program. To do this, add
auto to the end of the URL, as shown below:
After you start the Oracle9i Application Server, you can check to ensure that all JServ processes have started normally. If performance is degraded during operation, you can quickly determine if this is because JServ processes have terminated by looking at the Status column (each configured process has a status of
jserv.conffile to enable monitoring and specify the host(s) that can access JServ status (the default is
localhost). Be aware of security implications when selecting the hosts that will be allowed to access status information on your system.
The port must be the port on which the web server listens (found in the
httpd.conf file). A Configured Hosts column displays links to hosts.
The JServ status information for the host displays as shown in Figure 2-4.