Though the object graph is serialized on disk, it is also fully sent to memory for performance reasons.
Tuning
Basic Tuning
In the Administration Console, you can adjust:
• The number of aggregation threads in Consolidation > Advanced Settings. For example, if you set it to 4, you get 4 transformation workers, 4 aggregation workers, and 4 forwarders (* by number of forward rules), all potentially running in parallel for an incremental batch.
• Your commit conditions to fit your current scenarios
Get the Initial Scan Recommended Settings
1. In Consolidation > Commit triggers, specify a commit trigger based on No. of tasks to 500,000 tasks.
2. Specify a commit trigger based on Inactivity set to 1 task and 60s of inactivity.
3. Add an Aggregation trigger based Inactivity set to 1 task and 60s of inactivity (so your aggregation starts at the end of your initial push).
Get the Incremental Scan Recommended Settings
1. In Consolidation > Commit triggers, specify a commit trigger based on No. of tasks to 50,000 tasks.
2. Specify a commit trigger based on Inactivity set to 1 task and 60s of inactivity.
3. Adjust your aggregation triggers to fit your required freshness.
Advanced Tuning
In your <DATADIR>/config/Consolidation.xml file, you can add an AdvancedConfig node to ConsolidationConfig to tweak internal queues used during aggregation. It might increase throughput with more buffering, but you must take it into account in your sizing.