Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. B2B transformation
  7. Aggregator transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence Generator transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation

Transformations

Transformations

Optimizing the cache size

Optimizing the cache size

For optimal mapping performance, configure the cache sizes so that
Data Integration
can run the complete transformation in the cache memory.
  1. On the
    Advanced
    tab of the transformation properties, set the tracing level to verbose initialization.
  2. Run the task in auto cache mode.
  3. Analyze the transformation statistics in the session log to determine the cache sizes required for optimal performance.
    For example, you have a Joiner transformation called "Joiner." The session log contains the following text:
    CMN_1795 [2023-01-06 16:16:59.026] The index cache size that would hold [10005] input rows from the master for [Joiner], in memory, is [8437760] bytes CMN_1794 [2023-01-06 16:16:59.026] The data cache size that would hold [10005] input rows from the master for [Joiner], in memory, is [103891920] bytes
    The log shows that the index cache size requires 8,437,760 bytes and the data cache requires 103,891,920 bytes.
  4. On the
    Advanced
    tab of the transformation properties, enter the value in bytes that the session log recommends for the cache sizes.

0 COMMENTS

We’d like to hear from you!