About the Resource Utilization Graph

Describes how to use the data the Resource Utilization graph provides for capacity planning and understanding the health of the runtime environment.

The Resource Utilization graph tracks the following variables, which you can use to analyze the overall health of the runtime and calculate the available capacity for additional projects and orchestrations:
  • % Disk Used
  • % Memory Used
  • GC Activity
  • # Running Jobs

% Disk Used

This variable tracks the percentage of disk space used by orchestration job variables and historical data.

When you run an orchestration job, the runtime uses the disk to store the variable data for that job. When you enable persistence, the stored variable data for jobs allows the Integration Appliance to provide a point-in-time recovery of orchestration jobs should the Integration Appliance encounter a fault that requires restarting the runtime.

The runtime also stores historical data about orchestration jobs, which you can view on the Web Management Console (WMC) Job Log page.

If the amount of disk space available becomes too low, the Integration Appliance generates an alert, which sends a notification to designated users.

% Memory Used

The Integration Appliance has a fixed amount of available memory to run orchestrations. The % Memory Used variable tracks the amount of this fixed memory used by orchestration jobs and the corresponding variable data. When the memory allocated to orchestration jobs and variable data is no longer being used, the memory is returned to the pool of available memory using a process called garbage collection.

There is a direct relationship between the amount of memory used and garbage collection cycles. However, high memory usage does not necessarily mean an increase in full garbage collection cycles.

For more information about factors that affect the amount of memory used, see Best Practices for Memory Management.

GC Activity

Garbage collection is a process that returns memory, held by completed jobs and variable data, back to a pool of memory used by all orchestration jobs. This garbage collection process ensures that the Integration Appliance has a constant supply of free memory to be used by new orchestration jobs.

The GC Activity variable tracks the percentage of full garbage collections that occur in a minute. This percentage is calculated by dividing the number of full garbage collections by 6. Ideally, the GC activity should be at or below 50%, that is 3 full garbage collections per minute. Orchestration performance is severely degraded when 6 or more full garbage collections happen per minute.

For more information about garbage collection and factors that impact garbage collection, see Best Practices for Memory Management.

# Running Jobs

Displays the number of jobs currently running on the Integration Appliance.




Feedback | Notices


Timestamp icon Last updated: Friday, February 5, 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.appliance.doc/Monitoring/about_the_resource_utilization_graph.html