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

Sorter caches

Sorter caches

The
mapping
task passes all incoming data into the Sorter transformation before it performs the sort operation. The
mapping
task uses cache memory to process Sorter transformations. If the
mapping
task cannot allocate enough memory, the mapping fails.
By default, the
mapping
task determines the cache size at run time. Before starting the sort operation, the
mapping
task allocates the amount of memory configured for the Sorter cache size.
Configure the Sorter cache size with a value less than the amount of available physical RAM on the machine that hosts the Secure Agent. Allocate at least 16 MB (16,777,216 bytes) of physical memory to sort data with a Sorter transformation. When you allocate memory to the Sorter cache, consider other transformations in the mapping and the volume of data in the
mapping
task.
If the amount of incoming data is greater than the Sorter cache size, the
mapping
task temporarily stores data in the work directory. When storing data in the Sorter transformation work directory, the
mapping
task requires disk space of at least twice the amount of incoming data.
When you configure the tracing level to Normal, the
mapping
task writes the memory amount that the Sorter transformation uses to the session log.

0 COMMENTS

We’d like to hear from you!