To identify a mapping bottleneck, analyze the performance details in the mapping log. Performance details include information about each transformation, such as the number of input rows, output rows, and error rows.

You can also add a Filter transformation before each target definition. Set the filter condition to false so the Filter transformation loads no data into the target tables. If the time it takes to run the new mapping is the same as the original mapping, you have a mapping bottleneck.