Data Integration Performance Tuning

Back Next

Bottlenecks

The first step in performance tuning is to identify performance bottlenecks. Performance bottlenecks can occur in the source and target databases, the mapping, the mapping task, and the system.

Tuning a bottleneck may reveal another one. The strategy is to identify a performance bottleneck, eliminate it, and then identify the next performance bottleneck until you're satisfied with the performance.

Look for performance bottlenecks in the following order:

Target

Source

Mapping

Mapping task

System

Use the following methods to identify performance bottlenecks:

Run test mappings.: You can configure a test mapping to read from a flat file source or to write to a flat file target to identify source and target bottlenecks.
Analyze thread statistics.: Analyze thread statistics to determine the optimal number of partitions.
Monitor system performance.: You can use system monitoring tools to view the percentage of CPU usage, I/O waits, and paging to identify system bottlenecks.

Data Integration performance tuning overview

Thread statistics

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal