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

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!