Performance Tuning Guide

10.5.7
- 10.5.9
- 10.5.8
- 10.5.6
- 10.5
- 10.4.0

Back Next

Using Thread Statistics

You can use thread statistics in the session log to identify source, target, or transformation bottlenecks. By default, the Integration Service uses one reader thread, one transformation thread, and one writer thread to process a session. The thread with the highest busy percentage identifies the bottleneck in the session.

The session log provides the following thread statistics:

Run time.
Amount of time the thread runs.

Idle time.
Amount of time the thread is idle. It includes the time the thread waits for other thread processing within the application. Idle time includes the time the thread is blocked by the Integration Service, but not the time the thread is blocked by the operating system.

Busy time.
Percentage of the run time the thread is busy according to the following formula:

(run time - idle time) / run time X 100

You can ignore high busy percentages when the total run time is short, such as under 60 seconds. This does not necessarily indicate a bottleneck.

Thread work time.
The percentage of time the Integration Service takes to process each transformation in a thread. The session log shows the following information for the transformation thread work time:

Thread work time breakdown:
        <transformation name>: <number> percent
        <transformation name>: <number> percent
        <transformation name>: <number> percent

If a transformation takes a small amount of time, the session log does not include it. If a thread does not have accurate statistics, because the session ran for a short period of time, the session log reports that the statistics are not accurate.

Bottlenecks

Eliminating Bottlenecks Based on Thread Statistics

Example

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal