How often is a full online compaction (revision cleanup) run by default?

How often is a full online compaction (revision cleanup) run by default?

• A. Every week
• B. Every month
• C. Every 2 months
• D. Every 2 weeks

Answer: (A)

Regular maintenance of the repository’s revision history is needed to reclaim storage and keep performance stable. Full online compaction is the operation that cleans up old revisions and data blocks, compacting the store so it doesn’t grow indefinitely. This process is heavy and can impact performance, so it’s scheduled at a frequency that balances timely cleanup with minimizing disruption. By default, it runs once a week, which provides regular space reclamation without placing too much load on the system during peak usage. If your environment has unusually high revision activity, you might tune this setting, but the default is weekly.

Regular maintenance of the repository’s revision history is needed to reclaim storage and keep performance stable. Full online compaction is the operation that cleans up old revisions and data blocks, compacting the store so it doesn’t grow indefinitely. This process is heavy and can impact performance, so it’s scheduled at a frequency that balances timely cleanup with minimizing disruption. By default, it runs once a week, which provides regular space reclamation without placing too much load on the system during peak usage. If your environment has unusually high revision activity, you might tune this setting, but the default is weekly.