@nhrz I’m having the exactly same situation. This topic checked as it’s solved but how you solved it?
Even I select all options as to serve cached files to anonymous and known users it is still takes tiem to serve first visit.
-
This reply was modified 7 years, 3 months ago by
Kayacan AKIN.
Thread Starter
nhrz
(@nhrz)
@kayacanakin I solved the issue by activating pre-loading cache and manually starting it as well. I saw that no pages were being cached and so turning pre-load on ensures they are actually being cached, and I now get served the cached page all the time
One of the best ways of figuring out why a page isn’t being cached is by using the debug log in the plugin. Look at that after you load the page and you might see an error message that explains what went wrong.
Thread Starter
nhrz
(@nhrz)
I have to take things back. It indeed still seems to be on-going. I can’t get the cache to work.
I started everything over now, from scratch, for debugging purposes. I cleared all the previous cache. Went into “Debug” and activated cache message and then started the pre-fetch process.
The whole page is now cached. Any browser I visit the page from is blazingly fast. Debug shows no issues — cache is being loaded properly. However, when I open the source of any cached page, the cache message isn’t there. And I’m suspecting my previous issue will persist. In a few hours, when the cache is a few hours old, when I visit any of the previously cached pages, they will take a while to load once again. And then they will, once again, be cached.
I have no idea why the cache expires like this, when all settings should make it not expire at all. And maybe the lack of cache message in the source has got something to do with this?
I’m clueless. Everything works now. In a few hours, however, when visiting the page, it’ll be as if it’s not even cached, once again
@nhrz – the plugin deletes cache files that are too old. Look in the advanced settings page to change that number but that’s the way it’s supposed to work.
Or you can enable preload mode so garbage collection is disabled but then pages might get stale and not update properly.
Thread Starter
nhrz
(@nhrz)
My pages are static and don’t change unless I change them so I’m fine with having to clear the cache when I want the page to update
I’ve set “Cache Timeout” to 0 under “Advanced”. “Timer” among those same settings is at 600, fwiw. “Update preload cached files” under “Preload” is at 600. Not sure if any of these settings matter. But I just tried it now — an hour after I posted my earlier comment, and the cache is already “outdated”. I visited a page that was cached just an hour ago, and it now took a few seconds to load, as if it wasn’t cached at all. All subsequent refreshes are now instant.
The cache-message still doesn’t appear in the source.
So I’ve disabled the plugin deleting old cache files, from what I can see. And I’ve enabled preload mode, and preload mode updates every 600 minutes. This effect is still present and I can’t get the cache files to be served for longer than an hour or so
-
This reply was modified 7 years, 3 months ago by
nhrz.
-
This reply was modified 7 years, 3 months ago by
nhrz.
Thread Starter
nhrz
(@nhrz)
Fixed. Finally. The issue was with the “Update preload cache files” setting under “Preload”. This needs to be set to 0, so it never updates them. Otherwise you get the above issue. This should be a clearer as it’s not at all clear there’s a correlation Thank you