2. Source3. Mapping4. Session5. SystemUse the following methods to identify performance bottlenecks:
Run test sessions.
You can configure a test session to read from a flat filesource or to write to a flat file target to identify source and target bottlenecks.
Analyze performance details.
Analyze performance details, such asperformance counters, to determine where session performance decreases.
Analyze thread statistics.
Analyze thread statistics to determine the optimalnumber of partition points.
Monitor system performance.
You can use system monitoring tools to viewthe percentage of CPU use, I/O waits, and paging to identify systembottlenecks. You can also use the Workflow Monitor to view system resourceusage.
The most common performance bottleneck occurs when the Integration Servicewrites to a target database. Small checkpoint intervals, small database networkpacket sizes, or problems during heavy loading operations can cause targetbottlenecks.
Identifying Target Bottlenecks
To identify a target bottleneck, complete the following tasks:Configure a copy of the session to write to a flat file target. If the sessionperformance increases significantly, you have a target bottleneck. If a sessionalready writes to a flat file target, you probably do not have a target bottleneck.Read the thread statistics in the session log. When the Integration Servicespends more time on the writer thread than the transformation or reader threads, you have a target bottleneck.
Eliminating Target Bottlenecks
Complete the following tasks to eliminate target bottlenecks:Have the database administrator optimize database performance by optimizingthe query.Increase the database network packet size.Configure index and key constraints.
Performance bottlenecks can occur when the Integration Service reads from asource database. Inefficient query or small database network packet sizes cancause source bottlenecks.
Identifying Source Bottlenecks