Table of Contents

Search

  1. Preface
  2. Performance Tuning Overview
  3. Target Optimization
  4. Source Optimization
  5. Transformation Optimization
  6. Mapping Optimization
  7. Partitioned Mapping Optimization
  8. Run-time Optimization
  9. SQL Data Service Optimization
  10. Web Service Optimization
  11. Connections Optimization
  12. Data Transformation Optimization

Performance Tuning Guide

Performance Tuning Guide

Sorter Transformation Optimization

Sorter Transformation Optimization

Sorter transformations can slow performance when the physical RAM on the Data Integration Service node does not have enough memory allocated to sort data.
Consider the following solution for Sorter transformation bottlenecks:
Allocate sufficient memory.
For optimal performance, configure the Sorter cache size with a value less than or equal to the amount of available physical RAM on the Data Integration Service node. Allocate at least 16 MB of physical memory to sort data using the Sorter transformation. The Sorter cache size is set to 16,777,216 bytes by default. If the Data Integration Service cannot allocate enough memory to sort data, it fails the mapping.
If the amount of incoming data is greater than the amount of Sorter cache size, the Data Integration Service temporarily stores data in the Sorter transformation work directory. The Data Integration Service requires disk space of at least twice the amount of incoming data when storing data in the work directory.

0 COMMENTS

We’d like to hear from you!