Share this page

# Web Server Resources graphs

The Web Server Resources graphs provide you with information about the resource usage of the Microsoft IIS and Apache Web servers during performance test execution.

In this topic:

## Overview

Web Server Resources graphs provide you with information about the resource usage of the Microsoft IIS and Apache Web servers during performance test execution. In order to obtain data for these graphs, before running the load test scenario, you need to activate the online monitor for the server and specify which resources you want to measure. For information on activating and configuring the Web Server Resource monitors, including the performance counters see Web Server Resource monitoring.

In order to display all the measurements on a single graph, Analysis may scale them. The Legend window indicates the scale factor for each resource. To obtain the true value, multiply the scale factor by the displayed value.

Back to top

## Apache Server graph

The Apache Server graph displays a summary of resources on your Apache Web server. This graph shows server statistics as a function of the elapsed load test scenario time.

Note: To obtain data for this graph, from Controller and before running the scenario, you need to enable the Apache online monitor and select the default measurements you want to display.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | The resource usage on the Apache server during the scenario run.

Apache server measurements

The following default measurements are available for Apache servers:

Measurement | Description
--- | ---
# Busy Servers | The number of servers in the Busy state
# Idle Servers | The number of servers in the Idle state
Apache CPU Usage | The percentage of time the CPU is utilized by the Apache server
Hits/sec | The HTTP request rate
KBytes Sent/sec | The rate at which data bytes are sent from the web server

Sample scenario

A sample graph may show that the CPU usage remained steady throughout the scenario. At the end of the scenario, the number of idle servers increased, but the number of busy servers remained steady at 1 throughout the scenario, implying that the Vuser only accessed one Apache server.

The scale factor for the Busy Servers measurement is 1/10 and the scale factor for CPU usage is 10.

Back to top

## Microsoft Information Internet Server (IIS) graph

The Microsoft Information Internet Server(IIS) graph displays a summary of resources on MS IIS web server. This graph shows server statistics as a function of the elapsed load test scenario time.

Note: To obtain data for this graph, from Controller and before running the scenario, you need to enable the MS IIS online monitor and select the default measurements you want to display.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | The resource usage on the MS IIS.

IIS server measurements

The following default measurements are available for the IIS server:

Object | Measurement | Description
--- | --- | ---
Web Service | Bytes Sent/sec | The rate at which the data bytes are sent by the web service.
Web Service | Bytes Received/sec | The rate at which the data bytes are received by the web service.
Web Service | Get Requests/sec | The rate at which HTTP requests using the GET method are made. Get requests are generally used for basic file retrievals or image maps, though they can be used with forms.
Web Service | Post Requests/sec | The rate at which HTTP requests using the POST method are made. Post requests are generally used for forms or gateway requests.
Web Service | Maximum Connections | The maximum number of simultaneous connections established with the web service.
Web Service | Current Connections | The current number of connections established with the web service.
Web Service | Current NonAnonymous Users | The number of users that currently have a non-anonymous connection using the web service.
Web Service | Not Found Errors/sec | The rate of errors due to requests that could not be satisfied by the server because the requested document could not be found. These are generally reported to the client as an HTTP 404 error code.
Process | Private Bytes | The current number of bytes that the process has allocated that cannot be shared with other processes.

Sample scenario

In a typical scenario, you might find that the Bytes Received/sec and Get Requests/sec measurements remain fairly steady throughout the scenario, while the % Total Processor Time, Bytes Sent/sec, and Post Requests/sec measurements fluctuate considerably.

The scale factor for the Bytes Sent/sec and Bytes Received/sec measurements is 1/100, and the scale factor for the Post Requests/sec measurement is 10.

Back to top

See also:

- Web Server Resource monitoring

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: