Hello,
Are you referring to Cached pages or objects? Are both DB cache and Object cache enabled?
Thread Starter
T4ng
(@schwipps)
DB Cache and object cache are both enabled (memcached).
As I understand it, objects influence page caching/speed delivery.
The settings I’m talking about are:
Page cache : Maximum lifetime of cache objects (Garbaged is only for disk caching)
Object cache : Default lifetime of cache objects, and Garbage collection interval
My Database cache current settings :
Maximum lifetime of cache objects:3600
Garbage collection interval: 7200
Should I also set these 2 last settings to that same 21600 value? Any drawback to consider?
Hello,
How long a page is cached, depends on the value of Browser Cache => HTML & XML => Expires header lifetime
Thread Starter
T4ng
(@schwipps)
Changed that settings too, and indeed, the preloaded pages now have a 6 hours lifetime, and will renew much less often, as expected.
However… I still find many of my pages not preloaded: when I take a look at the response of some sitemap declared pages, the headers state the page was last-modified at the exact same moment I opened it, whenever it should have been created somewhere in the last 6 hours, if properly warmed up.
The settings allow way enough time to warm up every page, so why so many pages won’t get warmed up as supposed to?
Thread Starter
T4ng
(@schwipps)
Do you need more informations to troubleshoot this issue?
Hello,
Are you using a server cronjob (using crontab) to run WordPress scheduled events? If not, the preloader will only be triggered at the end of every request, which is not that often in your case.
Thread Starter
T4ng
(@schwipps)
Hi Marko,
Yes, we do use a cronjob, so that the preloader get triggered every 2 minutes.
Hello,
Does your sitemap contain all the pages?
Thread Starter
T4ng
(@schwipps)
Not all, but most of the pages are in the sitemaps. And on a regular basis, some of pages that are in the sitemaps but won’t get preloaded.
Thread Starter
T4ng
(@schwipps)
I also checked for these pages that they were set as indexable through Yoast SEO.
Hello @schwipps,
You should add logging. Logging is available in wp-cli now.
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.
Thread Starter
T4ng
(@schwipps)
I can already see, from the server logs, which page have been crawled by the preload or not. Would this method will give us more details about what goes wrong?
Hello,
Yes, as suggested in the previous post.
