Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Caches in production systems do not require manual clearing

Updated on April 25, 2019


A system administrator asks:

Process Commander uses multiple memory and disk caches,, and each user has an Internet Explorer cache on the workstation.  

In a development system, it's to be expected that certain caches need to be cleared for various purposes. 

But in a production setting, where the pace of rule change is much slower, are there any caches that should be cleared routinely? Does it depend on how long the system stays up?

Is there any need to flush any of the caches, either for accuracy or for performance, in a production system -- in which no rules change or rules change only slowly?


Process Commander is designed to have high availability and high performance, even during extended periods of uptime. In a production setting, there are no requirements for periodic clearing of any cache, and no benefits from doing so.

System data is saved into the file system and/or is collected in in-memory caches.  The in-memory caches are self-regulating, having high-water settings that govern their discarding of least-used material.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us