Table of Contents

Search

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