Configure the autosave threshold
This page explains how to configure the FileVault autosave threshold used during package installations. Use this option to balance performance and memory usage during large imports. If the threshold is set too high, memory consumption can grow significantly; if it is set too low, frequent saves may add overhead.
Configuration
In Magnolia 6.2, configure the autosave threshold using Magnolia properties. You can also use the MicroProfile Config in Magnolia 6.3.
magnolia.packagemanager.import.autoSaveThreshold=512 (1)| 1 | Number of modified nodes that trigger a save during package installation.
Using MAX_VALUE should prevent any save action from being triggered, including both intermediate and final saves. |
| Default is 1024 nodes if not configured. |
Usage guidance
Optimize large content imports by strategically tuning the autosave threshold. Lower values save more frequently and keep the instance responsive longer during large imports, at the cost of slightly more overhead. Higher values save less frequently and can be faster, but increase memory use as changes accumulate. Balance performance and memory by setting the threshold based on content volume and environment.