Table of Contents

Search

  1. Preface
  2. Performance Tuning Overview
  3. Bottlenecks
  4. Optimizing the Target
  5. Optimizing the Source
  6. Optimizing Mappings
  7. Optimizing Transformations
  8. Optimizing Sessions
  9. Optimizing Grid Deployments
  10. Optimizing the PowerCenter Components
  11. Optimizing the System
  12. Using Pipeline Partitions
  13. Performance Counters

Performance Tuning Guide

Performance Tuning Guide

Using Pipeline Partitions Overview

Using Pipeline Partitions Overview

After you tune the application, databases, and system for maximum single-partition performance, you may find that the system is under-utilized. At this point, you can configure the session to have two or more partitions.
You can use pipeline partitioning to improve session performance. Increasing the number of partitions or partition points increases the number of threads. Therefore, increasing the number of partitions or partition points also increases the load on the nodes in the Integration Service. If the Integration Service node or nodes contain ample CPU bandwidth, processing rows of data in a session concurrently can increase session performance.
If you use a single-node Integration Service and you create a large number of partitions or partition points in a session that processes large amounts of data, you can overload the system.
If you have the partitioning option, perform the following tasks to manually set up partitions:
  • Increase the number of partitions.
  • Select the best performing partition types at particular points in a pipeline.
  • Use multiple CPUs.