Mapping Optimization:
Some of the optimization techniques can be incorporated while designing the mapping & sessions, thus reducing the time & resources needed later to tune the mapping & sessions.
The most common bottlenecks occur when Informatica writes to the Target database. You can identify the bottlenecks by following methods:
- Running test sessions: Configure a test session, for the Source and/or Targets to Read/Write to a file. By this you can find the Source or Target bottlenecks.
- Studying Performance Details: You can set the option to collect performance details, to identify the session bottlenecks. Performance details provide information such as buffer input and output efficiencies.
- Monitoring system performance: You can use system-monitoring tools to view percent CPU usage, I/O waits and paging to identify the system bottlenecks.
Once the bottleneck location is identified, then these need to be eliminated. These can be categorized as:
1. Source & Target Database Bottlenecks: Need to ask the DBA to optimize the database tables by creating an index, configuring key constraints, increasing the database network packet size or optimizing the query.
2. Mapping Bottlenecks: Fine-tune the pipeline logic and transformation settings and options in the mappings to eliminate the mapping bottlenecks.
3. Session bottlenecks: You can optimize the session performance by using the performance details to tune the configuration settings in the session.
4. System bottlenecks: System administrator needs to analyze the system monitoring tools information and improve the CPU & network performance.
Posts
