Support » Plugin: Autoptimize » Also aggregate inline CSS causing infinitely growing cache size

  • Resolved courageous999

    (@courageous999)


    Hi,

    Up until yesterday we did not have either “Also aggregate inline CSS” nor “Also aggregate inline JS” checked because we had problems with overly fast growing cache when doing so.

    But lately, we have been having problems with too many requests when visiting a page on the site that Google didn’t like.
    And so, in an effort to resolve this, running some tests proved that there’s render blocking JS and aggregating the inline JS/CSS would fix most of the problems.

    Having said that, I went ahead and checked the “Also aggregate inline CSS” and right away the cache size (which would normally stay for months at less than 30%) grew from 20% to 30%. Having noticed that, I decided to not check the “Also aggregate inline JS” until I can confirm that the cache size will stabilize.

    Next thing you know, I came back today in the morning to a cache size of 1.3GB and an email of a too large cache warning. Within about an hour or 2 of noticing that, I checked again and the cache size was 1.48GB so it was still growing.

    I went into the Autoptimize cache directory, and the JS folder seemed normal with a size of 32MB whereas the CSS folder had this:
    https://www.dropbox.com/s/86nn05ctjridq7p/Screenshot%202019-07-18%2014.24.39.png?dl=0
    Upon noticing how recent the last few CSS files were created, I decided to do a normal refresh of the website’s homepage to see if that somehow generated one of those files. Unfortunately, what I suspected was true; for some reason a new CSS file is being generated every time the site is refreshed.

    Any ideas what we can do besides disabling “Also aggregate inline CSS”?

    Having a large cache size is one thing, which we can deal with to solve our “too many requests” Google problem, but having an infinitely growing large cache (about 1GB or more per day) is a bit too much.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 76 through 79 (of 79 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    Try comparing 2 pages or 2 blogposts and see if they use the same Autoptimized CSS? You might even have to check if there are differences between different days.

    Thread Starter courageous999

    (@courageous999)

    I decided to wait a week or 2 to see how fast the growth of the cache is.

    It seems to stop growing unless the plugins on the site are updated. So the more frequently the plugins get updated (i.e. every week) the faster the cache size grows. I suppose it makes sense but it’s a bummer since after updating the plugins today, within 2 hours the cache size grew by 5%.

    I imagine the above behavior is due to the newly generated autoptimize CSS/JS files, and since the old autoptimize files are kept, the cache size just grows. But at this rate, the cache will always grow in size.

    So I’m wondering, do the old files get automatically deleted after a period of time or no?
    And would it be a good idea to use the filter to increase the capacity of the cache (so that the red 100% isn’t reached so soon) now that we know it is growing at a normal growth rate?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    So I’m wondering, do the old files get automatically deleted after a period of time or no?

    no, AO never removes JS/ CSS from cache.

    And would it be a good idea to use the filter to increase the capacity of the cache (so that the red 100% isn’t reached so soon) now that we know it is growing at a normal growth rate?

    you could 🙂

    Thread Starter courageous999

    (@courageous999)

    Great! Thanks Frank

Viewing 4 replies - 76 through 79 (of 79 total)
  • The topic ‘Also aggregate inline CSS causing infinitely growing cache size’ is closed to new replies.