Configure Mem Reduct Threshold-Based Cleaning
Threshold cleaning responds to a configured memory-use level. Choose a threshold only after observing normal usage, and test it separately from interval cleaning. A low threshold can repeatedly trigger cleanup during normal work without fixing the application that continues allocating memory.
What matters for this task
Separate the trigger from the diagnosis. A memory percentage says how much is currently used; it does not explain why, whether Windows can reclaim cached pages, or whether the system is close to its commit limit. The 3.5.2 source defines a 90% threshold value, but that value is not proof of an optimal setting for every machine.
Steps to follow
- Observe a normal session with automatic cleaning disabled. Record the typical range and the point at which you actually notice a slowdown or allocation error.
- Keep interval cleaning off while testing a threshold. This makes it possible to tell which mechanism caused a cleanup notification or a pause.
- Set a threshold that does not continuously fire during ordinary steady usage. Change it in one direction at a time and note the resulting cleanup frequency.
- Repeat the workload and compare responsiveness and memory pressure. If the same application immediately consumes the memory again, investigate that application rather than lowering the threshold further.
Check the result
A useful threshold should not create repeated cleanup cycles under a steady workload. Verify the configuration after restarting the utility and make sure the trigger you intended to disable stays disabled.
Limitations and precautions
Do not use a threshold to hide a steadily growing memory leak. Record the growth and identify the responsible process.
Questions and answers
Can threshold and interval cleaning both be enabled?
They are separate mechanisms. Test one at a time first so that any result can be attributed to a specific trigger.
Why does cleaning happen again almost immediately?
Usage may still exceed the threshold or quickly return above it. Check the workload and whether another trigger is also enabled.
Sources and evidence
Product statements use the tagged release documentation. Diagnostic steps are proposed checks, not claimed laboratory results.