Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Raul P.

    (@alignak)

    That amount of data is relatively small depending on your site settings.
    You likely have some CSS that has dynamic classes, so it changes on every pageview and creates a new cache.
    You need to inspect it, see where it comes from and exclude that file via the ignore list.

    Thread Starter steemansnick

    (@steemansnick)

    This is only happening since the last update(s?).
    Tried to find that css file, but didn’t find anything so far.

    Plugin Author Raul P.

    (@alignak)

    On the screenshot, your cache has only 890 rows and 150 Mb of data.

    The cache table includes minified versions of your css and js files, but it’s unlikely that you have 890 files. That means, one or more css or js files are dynamic and keep changing on every pageview.

    Someone needs to inspect what is on the database and see if that is the case.

    Yes, version 3 started using the database to keep track of the intermediate minification cache, so it’s normal that it shows up now. Before it was similar, except that it created files instead.

    You can purge the cache from FVM using the top wp-admin bar.
    That will clear the cache and the table, but it will grow up again until you exclude the offending dynamic file from minification.

    Thread Starter steemansnick

    (@steemansnick)

    Hi Raul,

    thanks for your reply.

    Yes, every time the page refreshes a few new entries in the wp_fvm_cache table appear. I already had to exclude some js files so if now I also have to start excluding css files the point of the plugin is going to waste. After inspecition I’ve excluded some css files, but without result.

    I really like your plugin and I’m using it on a lot of sites for a long time already, but now it seems I have to go and search for another plugin / solution. Pity.

    Example: https://vp-recruitment.be/

    Thanks again.

    Plugin Author Raul P.

    (@alignak)

    You only need to exclude the files that change, not all of them. That’s just how your site is built. Changing to another plugin will still have the same issue, except that instead of growing the database, it will grow on your disk until you run out of space.

    Thread Starter steemansnick

    (@steemansnick)

    Sadly I had to disable the FVM plugin on all websites. I’ve tried what you said and numerous other things. The problem persist and/or there is no middle way solution. I’m on the lookout now for a new cache/minify plugin. That sucks because I really liked FVM.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Database overload’ is closed to new replies.