Large cache issue

  • Resolved bvedgie

    (@bvedgie)


    1 year, 4 months ago

    Hello team,

    Like a lot of users, I’m facing of a large cache issue for a month or more and have to flush it twice a day. It’s not manageable at all.

    Can you help debugging this? Our config seems to be fine and we’ve read almost all the docs and faq about that kind of issue. Nothing’s better.

    Can you help me analyze and find which element (plugin, .js, .css) is taking all the cache in order to exclude it?
    Thanks in advance.

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

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

    (@optimizingmatters)

    so what is you current configuration?

    • is CSS aggregated?
    • is inline CSS also aggregated?
    • is JS aggregated?
    • is inline JS also aggregated?
    Thread Starter bvedgie

    (@bvedgie)

    See our config here: AO config BV.

    Thanks

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    OK, can you temporarily disable “concatener les fichier CSS” to see if that makes the problem go away?

    Thread Starter bvedgie

    (@bvedgie)

    OK, I’ll try and let you know.

    Thread Starter bvedgie

    (@bvedgie)

    Know, the cache contains only 40 files for 1,04 Mb for a more than a day.

    I wonder if this is normal because usually the cache fills up very quickly.

    Any clue?

    Thanks

    Best regards

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, it confirms the problem is very likely due to the CSS being combined. Now as you had “also aggregate inline CSS” of and as wp-content/uploads and wp-content/cache were excluded from CSS aggregation, it are not the usual suspects that are bloating the cache.

    maybe as next step re-activate “aggregate CSS” but exclude wp-content/themes. if the problem is still not there, the issue is with one (or more) theme files, if it is not we’ll try with wp-content/plugins ?

    Thread Starter bvedgie

    (@bvedgie)

    Good morning,

    Excluding theme files directory from optimization is OK. The cache don’t bloat.

    I wonder if we could find exactly what files are the bad guys without testing each subdirectory.

    Thanks for your assistance .

    Best regards

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    yes you should be able to do that; themes/woodmart/css/parts seems to contain a lot of small(er) CSS files, but what might be happening is that the theme is smart in the sense that it loads those individual parts when required and that the combination of those parts-files is different for (almost) every page on your site. when aggregating that would result in a different aggregate CSS-file, resulting in a too big a cache.

    frank

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Large cache issue’ is closed to new replies.

Tags