pre load problems

  • Resolved Davod Yousefi

    (@davod473)


    2 years, 11 months ago

    Hello
    I have been using this plugin for a few days and I want to share my opinion.
    1- The cache section has flaws that when you update an article, comment, page or post, the entire system cache is emptied by default, and this is not good at all.
    2- The pre-loading part does not work properly and if you choose the number of pre-loading pages less and choose the time more, it will not pre-load all pages

    I have to select almost a thousand pages in each preload and select the preload time 1 second each time, which put a lot of load on the server and I get a 503 error.

    The problem occurs when your time cache is low and something is updated, the entire cache is cleared.

    3- In some cases, preloading cache is not done correctly, which is due to server resources.
    When I want to clear the cache of a specific page, it does not work properly and I have to clear the entire cache.

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

Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    2 years, 11 months ago

    Hello @davod473

    Thank you for reaching out and I am happy to assist you with this.

    1. When any page or post, comment is updated, the W3 Total Cache only purges the page in question and not the entire cache. If the entire cache is purged, something else amy be calling the w3tc_flush_all, and this may be some theme or a plugin.
      You can check this using the Purge log
    2. As for the Cache preloading, if you are relying to wp-cron, you may encounter problems like this if the cron is not fired for some reason. In this case, the next batch of the pages may not be preloaded and this is related as you mentioned to your server. Again, check the purge log and see what is calling the flus_all, as W3TC does not flush all cache once the page or an article is updated.
      If you do not want to rely on the wp-cron, you can use wp-cli, so, instead of calling wp-cron via crontab – you should call it directly via wp w3-total-cache pgcache_prime and track the output which pages / sitemap positions are primed by script.
    3. Can you please clarify what happens if you clear the cache of the specific page and how it does not work?

      Thanks!

Viewing 1 replies (of 1 total)

The topic ‘pre load problems’ is closed to new replies.