Performance Metrics for Capacity

OS Resource Monitoring

Average load - Average number of processes simultaneously in READY state the last minute
Collision rate - Collisions per second detected on the Ethernet
Context switches rate - Number of switches between processes or threads, per second
CPU utilization - Percent of time that the CPU is utilized
Disk rate - Rate of disk transfers
Incoming packets error rate - Errors per second while receiving Ethernet packets
Incoming packets rate - Incoming Ethernet packets per second
Interrupt rate - Number of device interrupts per second
Outgoing packets errors rate - Errors per second while sending Ethernet packets
Outgoing packets rate - Outgoing Ethernet packets per second
Page-in rate - Number of pages read to physical memory, per second
Page-out rate - Number of pages written to pagefile(s) and removed from physical memory, per second
Paging - Number of pages read to physical memory or written to pagefile(s), per second
Swap-in - Number of processes being swapped
Swap-out - Number of processes being swapped
System mode CPU utilization - Percent of time that the CPU is utilized in system mode
User mode CPU utilization - Percent of time that the CPU is utilized in user mode

Web Resource Monitoring

Hits Per Second - The Hits Per Second graph shows the number of hits (HTTP requests) to the Web server (y-axis) as a function of the elapsed time in the scenario (x-axis).
Throughput Graph - The Throughput graph shows the amount of throughput on the Web server (y-axis) during each second of the scenario run (x-axis). Throughput is measured in bytes and represents the amount of data that the Vusers received from the server at any given second.
HTTP Responses per Second - The HTTP Responses per Second graph shows the number of HTTP status codes
Pages Downloaded per Second - The Pages Downloaded per Second graph shows the number of Web pages (y-axis) downloaded from the server during each second of the scenario run (x-axis).
Retries per Second - The Retries Per Second graph shows the number of attempted Web server connections (y-axis) as a function of the elapsed time in the scenario (xaxis).

Oracle Resources

CPU used by this session - This is the amount of CPU time (in 10s of milliseconds) used by a session between the time a user call started and ended. Some user calls can be completed within 10 milliseconds and, as a result, the start and end user-call time can be the same. In this case, 0 milliseconds are added to the statistic. A similar problem can exist in the operating system reporting, especially on systems that suffer from many context switches.
CPU used when call started - The CPU time used when the call is started.
CR blocks created - A buffer in the buffer cache was cloned. The most common reason for cloning is that the buffer is held in an incompatible mode.
Cached Commit SCN referenced - The number of times cached Commit SCN is referenced
Commit SCN cached - The number of times Commit SCN is cached.
Current blocks converted for CR - A CURRENT buffer (shared or exclusive) is made CR before it can be used
DBWR buffers scanned - The total number of buffers looked at when scanning each LRU set for dirty buffers to clean. This count includes both dirty and clean buffers. Divide by DBWR LRU scans to find the average number of buffers scanned.
DBWR checkpoint buffers written - The number of buffers that were written for checkpoints
DBWR checkpoints - Number of times the DBWR was asked to scan the cache and write all blocks marked for a checkpoint
DBWR free buffers found - The number of buffers that DBWR found clean when it was requested to make free buffers. Divide by DBWR make free requests to find the average number of reusable buffers at the end of each LRU
DBWR lru scans - The number of times that DBWR does a scan of the LRU queue looking for buffers to write. This includes times when the scan is to fill a batch being written for another purpose, such as a checkpoint. This statistic is always greater than or equal to DBWR make free requests
DBWR make free requests - Number of messages received requesting DBWR to make some more free buffers for the LRU
DBWR revisited being-written buffer - The number of times that DBWR tried to save a buffer for writing and found that it was already in the write batch. This statistic is a measure of the amount of "useless" work that DBWR had to do in trying to fill the batch. This can occur because many sources contribute to a write batch. If the same buffer from different sources is considered for adding to the write batch, then all but the first attempt will be "useless" since the buffer is already marked as being written
DBWR summed scan depth - The current scan depth (number of buffers examined by DBWR) is added to this statistic every time DBWR scans the LRU for dirty buffers. Divide by DBWR lru scans to find the average scan depth
DBWR undo block writes - The number of transaction table blocks written by DBWR. It is an indication of how many "hot" buffers were written, leading to write complete waits
DDL statements parallelized - The number of DDL statements that were parallelized
DML statements parallelized - The number of DML statements that were parallelized
PX local messages received - The number of local messages received for Parallel Executions
PX local messages sent - The number of local messages sent for Parallel Executions
PX remote messages received - The number of remote messages received for Parallel Executions
PX remote messages sent - The number of remote messages sent for Parallel Executions
SQL*Net roundtrips to/from client - Total number of Net8 messages sent to and received from the client
SQL*Net roundtrips to/from dblink - Total number of Net8 messages sent over and received from a database link
Unnecessary process cleanup for SCN batching - The total number of times that the process cleanup was performed unnecessarily because the session/process did not get the next batched SCN. The next batched SCN went to another session instead
Background checkpoints completed - The number of checkpoints completed by the background. This statistic is incremented when the background successfully advances the thread checkpoint
Background checkpoints started - The number of checkpoints started by the background. It can be larger than the number completed if a new checkpoint overrides an incomplete checkpoint. This only includes checkpoints of the thread, not individual file checkpoints for operations such as offline or begin backup. This statistic does not include the checkpoints performed in the foreground, such as ALTER SYSTEM CHECKPOINT LOCAL
Bytes received via SQL*Net from client - The total number of bytes received from the client over Net8
Bytes received via SQL*Net from dblink - The total number of bytes received from a database link over Net8
Bytes sent via SQL*Net to client - The total number of bytes sent to the client from the foreground process(es)
Bytes sent via SQL*Net to dblink -The total number of bytes sent over a database link

Apache Web Server

Apache CPU Usage - 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

Oracle 9i Application Server

handle.min - Time The minimum time spent in the module handler
handle.avg - The average time spent in the module handler
handle.active - The number of threads currently in the handle processing phase
handle.time - The total amount of time spent in the module handler
handle.completed - The number of times the handle processing phase was completed
request.max - Time The maximum amount of time required to service an HTTP request
request.min - Time The minimum amount of time required to service an HTTP request
handle.min - Time The minimum time spent in the module handler
handle.avg - The average time spent in the module handler
handle.active - The number of threads currently in the handle processing phase
handle.time - The total amount of time spent in the module handler
handle.completed - The number of times the handle processing phase was completed
request.max - Time The maximum amount of time required to service an HTTP request
request.min - Time The minimum amount of time required to service an HTTP request
request.avg - The average amount of time required to service an HTTP request
request.active - The number of threads currently in the request processing phase
request.time - The total amount of time required to service an HTTP request
request.completed - The number of times the request processing phase was completed
connection.maxTime - The maximum amount of time spent servicing any HTTP connection
connection.minTime - The minimum amount of time spent servicing any HTTP connection
connection.avg - The average amount of time spent servicing HTTP connections
connection.active -The number of connections with currently open threads
connection.time - The total amount of time spent servicing HTTP connections
connection.completed - The number of times the connection processing phase was completed
numMods.value - The number of loaded modules
childFinish.count - The number of times the Apache parent server started a child server, for any reason
childStart.count - The number of times “children” finished “gracefully.” There are some ungraceful error/crash cases that are not counted in childFinish.count
Decline.count - The number of times each module declined HTTP requests
internalRedirect.count - The number of times that any module passed control to another module using an “internal redirect”
cpuTime.value - The total CPU time utilized by all processes on the Apache server (measured in CPU milliseconds)
heapSize.value - The total heap memory utilized by all processes on the Apache server (measured in kilobytes)
pid.value - The process identifier of the parent Apache process
upTime.value - The amount of time the server been running (measured in milliseconds)The average amount of time required to service an HTTP request
request.active - The number of threads currently in the request processing phase
request.time - The total amount of time required to service an HTTP request
request.completed - The number of times the request processing phase was completed
connection.maxTime - The maximum amount of time spent servicing any HTTP connection
connection.minTime - The minimum amount of time spent servicing any HTTP connection
connection.avg - The average amount of time spent servicing HTTP connections
connection.active - The number of connections with currently open threads
connection.time - The total amount of time spent servicing HTTP connections
connection.completed - The number of times the connection processing phase was completed
numMods.value - The number of loaded modules
childFinish.count - The number of times the Apache parent server started a child server, for any reason
childStart.count - The number of times “children” finished “gracefully.” There are some ungraceful error/crash cases that are not counted in childFinish.count
Decline.count - The number of times each module declined HTTP requests
internalRedirect.count - The number of times that any module passed control to another module using an “internal redirect”
cpuTime.value - The total CPU time utilized by all processes on the Apache server (measured in CPU milliseconds)
heapSize.value - The total heap memory utilized by all processes on the Apache server (measured in kilobytes)
pid.value - The process identifier of the parent Apache process
upTime.value - The amount of time the server been running (measured in milliseconds)