300MB is not huge if it stabilizes somewhat.
if it keeps on growing that fast the next couple of days you can try:
* disabling “also aggregate inline CSS”
* if you have a theme that stores page-specific CSS in wp-content/uploads instead of inlining it you can also exclude that directory in your CSS optimization exclusions (I’ll probably add it to the default exclusions in the next release).
hope this helps,
frank
thanks frank,
i have the Divi theme from ET, and i-ve been monitoring the cache since this morning and it doesn`t seem to grow…
purging the cache should be done also with purgin the cache from my cloudflare account ?
i seem to remember that in the past when i used autopimize, purging the cache would result in showing my webpage really weird (due to CSS i belive) to the people who already accesed my site and are reloading the website from the CDN… a refresh always fixed that problem
purging the cache should be done also with purgin the cache from my cloudflare account ?purging the cache should be done also with purgin the cache from my cloudflare account ?
when purging AO’s cache, you should also purge any page cache you might have indeed (AO tries to do so, but can for example to trigger a CloudFlare cache purge).
