• Resolved veco

    (@veco)


    Hi, nice plugin! ^_^
    So,.. today I had to empty the autoptimize cache because it had 831.93 MB from 3421 files.
    In less than 5 hours, I have about 1500 files in the wp-content/cache/autoptimize/css/ folder.. and more than 350 MB.
    I aggregate inline CSS and I have all the misc options checked.
    The space is not an issue but I was wondering if this is a normal behavior.. What can I do? The site was recently moved to a live environment.
    Thanks in advance!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    that’s a mighty fast growing cache you have there @veco. the reason is fast changing JS or CSS which causes AO cache misses. the easiest solution is not to aggregate inline JS and CSS and (if applicable) to exclude wp-content/cache or wp-content/uploads from CSS optimization (e.g. the Divi and Avada store non-static CSS there, so does the Elementor page-builder).

    hope this helps,
    frank

    Thread Starter veco

    (@veco)

    Hi again, and thanks for your quick reply. Actually I use Flatsome, which has it’s own page-builder. I’ll uncheck the aggregate inline css option and also optimize for logged in user, then I’ll just empty the cache again. How can I exclude those directories? It’s only the css’s doing because I only optimize html and css. Maybe in the near future I’ll be able to use your extension to actually optimize, cause I know it can do it ^_^ Also, on my test environment, the cache is small, is it because the lack of visitors? Just sayin’ ?? I’m not familiar with how it actually works.

    • This reply was modified 6 years, 7 months ago by veco.
    Plugin Author Optimizing Matters

    (@optimizingmatters)

    How can I exclude those directories?

    by adding them to the comma-separated CSS optimization exclusion list (only visible when “advanced options” are shown, so you might have to click that button near the top-right corner).

    Thread Starter veco

    (@veco)

    I didn’t know it works for directories ^_^
    With no inline css and disable autoptimize for logged on users, the cache is fine.
    Not sure if the plugin helps my site so much thou, with my current configurations. I’ll make some more tests. Thanks again for your quick support!
    Keep up the good work!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    inline CSS has no negative impact on performance, so you should be fine ??

    if you’re happy with the plugin and my support; feel free to leave a review here! ??

    have a nice day!
    frank

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘the cache is growing too fast’ is closed to new replies.