Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Data Integration performance tuning overview
  3. Optimizing targets
  4. Optimizing sources
  5. Optimizing mappings
  6. Optimizing mapping tasks
  7. Optimizing advanced clusters
  8. Optimizing system performance

Data Integration Performance Tuning

Data Integration Performance Tuning

Cloud connector performance

Cloud connector performance

Cloud data lake and cloud data warehouse connectors are designed for optimal data loading and unloading performance.
A common design pattern across these connectors is in the way Informatica stages data locally on disk before uploading to an end point or after downloading data from an end point. This staging process is a disk-intensive operation and requires both CPU and disk I/O resources. Keep this in mind for all cloud data lake to cloud data lake, cloud data lake to cloud data warehouse, and cloud data warehouse to cloud data warehouse integrations when SQL ELT optimization isn't used.
The following graph represents the performance of a concurrent cloud data warehouse mapping and the impact that sustained disk I/O has on it:
 This image shows how disk I/O impacts processing time. For example, the image shows that with 125 MB, execution time is 23 minutes and 1 second. With 500 MB, execution time is 7 minutes and 38 seconds.
Informatica recommends a storage device with 500 Mbps disk throughput for a
Data Integration
workload with either partitioning enabled or concurrent executions. For detailed information on the various tuning options for these endpoints, see the appropriate connector guides. Performance tuning articles are available in the Informatica Knowledge Base for some connectors.

0 COMMENTS

We’d like to hear from you!