• Resolved Feznizzle

    (@feznizzle)


    Hi,

    I check “Site Health” a few moments ago, found this message:
    “The scheduled event, w3_pgcache_prime, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.”

    I assume w3_pgcache_prime was trying to automatically build site cache? What can I do to fix this, make it so that it runs as scheduled?

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

    (@vmarko)

    Hello @feznizzle

    Thank you for your inquiry and I am happy to assist you with this.
    The event w3_pgcache_prime is for the Cache Preload. If you have enabled this option in Performance>Page Cache>Cache Preload and set the update interval, the priming is scheduled accordingly.
    As the Cache preload is starting from the top every time the post is updated or published it may skip the scheduled event depending on other schedules. However, this is normal behavior and there is nothing to worry about as your website cache will be primed.
    Thanks!

    Thread Starter Feznizzle

    (@feznizzle)

    Hi @vmarko,

    Ah, it’s comforting to hear that this is “normal”.

    I wonder about my settings, though. I’m on my own VPS, well provisioned and very fast. I decided to speed up my cache preloads.

    I have it set to:
    Automatically prime the page cache
    Update interval: 10 Seconds
    Pages per interval: 15

    Is that acceptable?

    • This reply was modified 4 years, 5 months ago by Feznizzle.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @feznizzle

    The default Update interval: is set to 15 mins as that is most optimal for most servers.
    I would advise that you increase the Update interval to 5-10 mins, just to make sure that all pages are being primed and to reduce unnecessary load on your server.
    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘w3_pgcache_prime is late to run’ is closed to new replies.