swapna

• Feb 10th, 2006

 

when the work flow is running slowly u have to find out the bottlenecks

in this order

target

source

mapping

session

system

rajendar

• Feb 11th, 2006

 

work flow may be slow due to different reasons one is alpa characters in decimal data check it out this and due to insufficient length of strings check with the sql override

dashingcar

 Profile Answers by dashingcar 

• Apr 19th, 2010

 

PowerCenter 8.1.1 Performance Tuning Guide
Generally, look for performance bottlenecks in the following order:

1. Target
2. Source
3. Mapping
4. Session
5. System

Use the following methods to identify performance bottlenecks:

Run test sessions. You can configure a test session to read from a flat file source or to write to a flat file target to identify source and target bottlenecks.

Study performance details and thread statistics. You can analyze performance details to identify session bottlenecks. Performance details provide information such as readfromdisk and writetodisk counters.

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.