I’m afraid not; auto-clearing AO’s cache could break sites entirely is the page cache is not cleared at the same moment. Additionally a fast growing cache is an indication of more important issues and can be prevented by changing the configuration (not aggregating (inline) JS/ CSS).
hope this clarifies,
frank
Thanks for your “frank” feedback, @optimizingmatters,
I read your cautionary tale and comprehended the hosted account that incurred “Out of Space” for the hosting was likely the sum composite of too many JavaScript files caching. The cache was burgeoning at 300 MB, with emails nearly full, causing the 2GB limit account to freeze up. Since I have been trying to keep the cache trimmed. Apparently, that approach defeats largely the purpose of caching in the first place. I will incrementally remove the cache cleaner across accounts and watch for cache size problems.
In my case, “Also aggregate inline JS?” is always unchecked. I used the Avada theme and they include a host of performance options that replicate many of the functions that Autoptimize provides, therefore I am careful to disable those features so as not to have two sources trying to perform the same optimizations.
Thanks for your clarifications!