Informatica

Bottlenecks in Informatica

The performance of informatica process gets slower due to this Bottlenecks. Performance tuning process identifies the bottlenecks and eliminate it to get a better acceptable ETL load time. Tuning starts with the identification of bottlenecks in source, target, mapping and further to session tuning.
Different types of bottlenecks in informatica.
  • Source Bottlenecks
  • Target Bottlenecks
  • Mapping Bottlenecks
  • Session Bottlenecks
  • System Bottlenecks
Source Bottlenecks
Performance bottlenecks can occur when the Integration Service reads from a source database. Slowness in reading data from the source leads to delay in filling enough data into DTM buffer. This delay causes the entire session to run slower. This bottleneck is also due to the source connection problems and incorrect source query.   
Target Bottlenecks
The target bottleneck occurs when the integration service writes to a target database. Small database checkpoint intervals, small database network packet sizes, or problems during heavy loading operations can cause target bottlenecks. 
Mapping Bottlenecks
Complex mapping logic and incorrect mapping logic can cause mapping bottleneck. When the integration service spends more time on one transformation mapping bottleneck occurred.
Session Bottlenecks
If we don't have source, target and mapping bottlenecks we may have session bottlenecks. Session bottleneck occurs normally when you have the session memory configuration is not turned correctly. Small cache size, small commit intervals, low buffer memory may cause session bottlenecks.
System Bottlenecks
The Integration Service uses system resources to process transformations, run sessions, and read and write data. The Integration Service also uses system memory to create cache files for transformations, such as Aggregator, Joiner, Lookup, Sorter, XML, and Rank.















Powered by Blogger.