InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.21: Performing tasks with the Resource Analyzer >
6.6.21.0: Performance data reported with the Resource Analyzer

6.6.21.0: Performance data reported with the Resource Analyzer

The following tables describe the counters for each resource category. Each table includes the following types of information:

  • Name. This column shows the name of the counter as it appears in the Counter Selection panel.

  • Granularity. This column indicates the unit to which data collection is applied for that counter.

  • Impact. This column identifies the level of performance impact--low, medium, or high-- that is expected when the counter is enabled.

  • Data Type. This column shows the digital representation format used for expressing the measurable units that are collected by the counter. The following types are included:

    • Long--This is a signed integer.

    • Stat--This is basic statistical data that is used to calculate means, variations, and standard deviation information. The Resource Analyzer uses the following raw data, which is stored on the application server: the sum, the count, and the sum of squares (for standard deviation calculations).

    • Load--This value adds a time dimension to calculate time-weighted statistics. The following raw data, which is stored on the application server, is used to perform the calculations::

      • The time-weighted sum, which is updated each time the counter is changed

      • The time when the counter is created

      • The time when the counter was last updated

      • The current value of the counter

  • For the enterprise beans resource category, Bean Type is also given. Values can be entity, stateful session, stateless session, and all.

Counters are available for the following resource categories:

Each resource category has an instrumentation level. The instrumentation level determines which counters are being collected for that category. Each counter has a cost rating (high, medium, or low), indicating its impact on an application's performance if data is collected for that counter. If a resource category has an instrumentation level of high, for example, all counters in that category with a high cost rating and lower are collected.

By default, instrumentation levels for each resource category are set to none. For information about how to set instrumentation levels, see Understanding instrumentation levels for data collection.


Counters for enterprise beans

The available performance data for enterprise beans depends on the type of bean: entity bean, stateful session bean, or stateless session bean. Every enterprise bean home interface has a single module of performance data, and all bean instances of that home are reflected in the statistics for that home. (The instances update the same set of counters as those selected in the single module for the performance data.) An object pool is a cache of bean objects. There is a cache for each home interface. Performance data for an object pool can be used to determine how effective the pool is (how often a bean object was available in the pool) and how many resources the pool used. In addition to enterprise bean data, data is collected for every method of a bean's remote interface.

The performance data for enterprise beans, object pools, and methods is listed in the following table. The notation of (ms) in the Name column indicates that the counter value is reported in milliseconds.

Table 1. Counter information for enterprise beans

Name Granularity Impact Bean type Data type Description
Num Creates Per type/ per home Low Entity and stateful session long Number of create calls.
Num Removes Per type/ per home Low Entity and stateful session long Number of remove calls.
Num Activates Per type/ per home Low Entity and stateful session long Number of times a bean instance was activated.
Num Passivates Per type/ per home Low Entity and stateful session long Number of times a bean instance was passivated.
Num Instantiates Per type/ per home Low All long Number of times bean objects were created.
Num Destroys Per type/ per home Low All long Average number of times bean objects were destroyed (garbage collected).
Num Loads Per type/ per home Low Entity long Number of times bean data was loaded.
Num Stores Per type/ per home Low Entity long Number of times bean data was written to the database.
Concurrent Actives Per type/ per home High Entity and stateful session load Average level as a function of time of bean instances of the home that are in the ready state (active beans). A measure of how busy the server is.
Concurrent Lives Per type/ per home High All load Average level as a function of time of bean objects that exist in the run time, whether active or pooled (objects that were instantiated but not yet destroyed). A measure of how many resources the home interface is consuming.
Total Method Calls Per type/ per home Low All long Total number of methods being processed. A measure of how busy the server is.
Avg Method Rt (ms) Per type/ per home Medium All stat Average response time on all methods of the remote interface for this bean.
Avg CreateTime (ms) Per persister/ per home Medium All stat Average method response time for create.
Avg Remove Time (ms) Per persister/ per home Medium All stat Average method response time for remove.
Active Methods Per type/ per home High All load Average number of invocations being processed concurrently for all the methods.
Gets from Pool Per home/ object pool Low All long Number of calls retrieving an object from the pool.
Gets Found Per home/ object pool Low All long Number of times a retrieval call found an object available in the pool.
Returns to Pool Per home/ object pool Low All long Number of calls returning an object to the pool.
Returns Discarded Per home/ object pool Low All long Number of times the returned object was discarded because the pool was already full.
Drains from Pool Per home/ object pool Low All long Number of times the pool was found idle and an attempt was made to remove idle objects.
Avg Drain Size Per home/ object pool Medium All load Average number of objects discarded each time the pool was emptied of idle objects.
Pool Size Per home/ object pool High All load Average number of objects in the pool.

Counters for database connection pools

Each data source (database instance) has a connection pool. Performance data for database connection pools is listed in the following table. The notation of (ms) in the Name column indicates that the counter value is reported in milliseconds.

Table 2. Counter information for database connection pools

Name Granularity Impact Data type Description
Num Creates Per connection pool Low long Number of connections created.
Num Destroys Per connection pool Low long Number of connections released.
Num Returns Per connection pool Low long Number of connections returned to the pool by applications.
Num Allocates Per connection pool Low long Number of connections allocated.
Pool Size Per connection pool High load Average size of the pool (number of connections).
Concurrent Waiters Per connection pool High load Average number of threads waiting for a connection.
Avg Wait Time (ms) Per connection pool Medium stat Average time that a client waited to be granted a connection.
Faults Per connection pool Low long Number of connection pool timeouts.
Percents Used Per connection pool High load Average percent of the pool in use.
Percents Maxed Per connection pool High load Average percent of the time that all connections are in use.
PrepStmt Cache Discards Per connection pool Low long Number of prepared statements discarded from the cache.

Counters for J2C connectors

Performance data for J2C Connectors is listed in the following table.

Table 3. Counter information for J2C Connectors

Name Granularity Impact Data type Description
Num Managed Connections Per connection factory Low long The number of physical connections in the pool.
Num Connections Per connection factory Low long The total number of connection handles in use by the application server.

Counters for the JVM run time

The performance data for the Java Virtual Machine (JVM) run time is listed in the following table.

Table 4. Counter information for JVM run-time memory

Name Granularity Impact Data type Description
Total Memory (bytes) Per JVM Low long The total amount of memory in the JVM run time
Free Memory (bytes) Per JVM Low long The amount of free memory in the JVM run time
Used Memory (bytes) Per JVM Low long The total amount of memory used in the JVM run time.

Counters for the JVMPI profiler

Resource Analyzer leverages a Java Virtual Machine Profiler Interface (JVMPI) to enable a more comprehensive performance analysis. This profiling tool enables the collection of information about the Java Virtual Machine (JVM) that runs the application server. For information on this tool, see Enabling JVMPI data reporting.

Table 5. Counter information for the JVMPI interface

Name Granularity Impact Data type Description
Num Calls Per JVM Low long The number of garbage collection calls issued.
Avg Time Between Calls Per JVM Low stat The average time in seconds between two garbage collection calls.
Avg Duration Per JVM High stat The average time a garbage collection call is in process.
Num Waiters Per JVM Low long The number of times a thread waits for a lock.
Avg Wait Time Per JVM Low stat The average time that a thread waits for a lock.
Num Objects Alloc Per JVM Low long The number of objects allocated.
Num Objects Freed Per JVM Low long The number of objects freed.
Num Objects Moved Per JVM High long The number of objects moved in the heap.
Num Threads Started Per JVM Low long The number of threads started.
Num Threads Dead Per JVM Low long The number of threads dead.

Counters for the servlet session manager

Performance data for HTTP sessions is listed in the following table.

Performance data for a servlet is collected only if the servlet is loaded when the application server is started. To ensure that data is collected for a servlet, see Starting data retrieval.

Table 6. Counter information for the servlet session manager

Name Granularity Impact Data type Description
Created Sessions Per servlet Low long Number of sessions that were created.
Invalidated Sessions Per servlet Low long Number of sessions that were invalidated.
Finalized Sessions Per servlet Low load Number of sessions that were finalized.
Session Lifetime Per servlet Medium stat Average lifetime of a session.
Session Invalidate Time Per session manager Medium stat Average time from when a session is invalidated to when it is finished.
Active Sessions Per servlet High load Total number of sessions that currently are being accessed by requests.
Live Sessions Per servlet High load Total number of sessions in the session manager cache.

Counters for ORB and Web container thread pools

The performance data for ORB and Web container thread pools is listed in the following table.

Table 7. Counter information for thread pools

Name Granularity Impact Data type Description
Thread Creates Per thread pool Low long Number of threads created.
Thread Destroys Per thread pool Low long Number of threads destroyed.
Active Threads Per thread pool High load Average number of active threads in the pool.
Pool Size Per thread pool High load Average number of threads in the pool.
Percent Maxed Per thread pool High load Average percent of the time the number of threads in the pool reached or exceeded the desired maximum number.

Counters for the transaction manager

The following performance data is available for container transactions.

Table 8. Counter information for transactions

Name Granularity Impact Data type Description
Global Trans Begun Per transaction manager/server Low long Total number of global transactions begun at the server.
Global Trans Involved Per transaction manager/server Low long Total number of global transactions involved at the server (begun and imported).
Local Trans Begun Per transaction manager/server Low long Total number of local transactions begun at the server.
Active Global Trans Per transaction manager/server High load Average number of concurrently active global transactions.
Active Local Trans Per transaction manager/server High load Average number of concurrently active local transactions.
Global Trans Duration Per transaction manager/server Medium stat Average duration of global transactions.
Local Trans Duration Per transaction manager/server Medium stat Average duration of local transactions.
Global Before Completion Duration Per transaction manager/server Medium stat Average duration for before_completion for global transactions.
Global Prepare Duration Per transaction manager/server Medium stat Average duration for prepare for global transactions.
Global Commit Duration Per transaction manager/server Medium stat Average duration for commit for global transactions.
Local Before Completion Duration Per transaction manager/server Medium stat Average duration for before_completion for local transactions.
Local Commit Duration Per transaction manager/server Medium stat Average duration for commit for local transactions.
Num Optimizations Per transaction manager/server Low long Number of global transactions converted to single phase for optimization.
Global Trans Committed Per transaction manager/server Low long Total number of global transactions committed.
Local Trans Committed Per transaction manager/server Low long Number of local transactions committed.
Global Trans RolledBack Per transaction manager/server Low long Total number of global transactions rolled back.
Local Trans RolledBack Per transaction manager/server Low long Number of local transactions rolled back.
Global Trans Timeout Per transaction manager/server Low long Number of global transactions timed out.
Local Trans Timeout Per transaction manager/server Low long Number of local transactions timed out.

Counters for Web applications

Performance data for Web applications is shown in the following table. Note that the first four counters are simply aggregate values for all of the servlets in the application. The notation of (ms) in the Name column indicates that the counter value is reported in milliseconds.

Table 9. Counter information for Web applications

Name Granularity Impact Data type Description
Num Loaded Servlets per servlet/JSP file Low long Current number of loaded servlets.
Num Reloads per servlet/JSP file Low long Number of times a servlet has been reloaded.
Total Requests per servlet/JSP file Low long Total number of requests for the servlets.
Concurrent Requests per servlet/JSP file High load Number of requests that are concurrently processed.
Response Time (ms) per servlet/JSP file Medium stat Response time until the request is finished.
Num Errors per servlet/JSP file Low long Number of errors or exceptions that have occurred in the servlets.
Go to previous article: Performing tasks with the Resource Analyzer Go to next article: Analyzing resources with the Java administrative console

 

 
Go to previous article: Performing tasks with the Resource Analyzer Go to next article: Analyzing resources with the Java administrative console