Cache: miss after crawl + warmer stops at 1000 visits

Update:

Okay it looks like the cache warmer does not stop after the 1000 visits, it just took a long break (couple hours). The cache is still a miss after the warm-up has completed. What I found is that the cache warmer takes the break at the ‘Speed limit’ (Crawler settings) I’ve set. Which is odd because the description says ‘Max pages to visit per minute’. Changing the speed limit to e.g. 5000 eliminated the long pause.

Two other little things:

• When I start a warm-up manually, the ‘Duration’ starts at 01:00:00 (?)
• In Cache Warmer settings > Schedule, scrolling is disabled/not working (?)

@identiden Thank you for the feedback.

I will investigate the “Speed limit” bug.

>In Cache Warmer settings > Schedule, scrolling is disabled/not working (?)

I did not disable it. Probably there is just nothing to scroll, as the page is pretty small. The latest option is “Posts warming enqueue interval”.

> When I start a warm-up manually, the ‘Duration’ starts at 01:00:00 (?)

I confirm this bug, though it starts at 06:00:00 for me.

So 2 valid bugs are reported from your side. Thanks!

And “miss” is not something we can control, as it depends on the cache solution settings.

Thank you for the replies!

>In Cache Warmer settings > Schedule, scrolling is disabled/not working (?)

I see, I didn’t know that the page length would impact the scrolling of the WP navigation menu.

What about the speed limit thing, it says “Max pages to visit per minute” but the warmer takes couple hour a ‘pause’ when it hits that limit?

As for the cache: miss, How do I check if I got served a cached page created by the Cache Warmer? There is no extra header added with this plugin, right? After the warmer is completed the pages don’t seem to load any faster.

I see, I didn’t know that the page length would impact the scrolling of the WP navigation menu.

@identiden Could you maybe record a video or send a screenshot? I don’t understand exactly what menu you’re talking about with the blocked scrolling.

What about the speed limit thing, it says “Max pages to visit per minute” but the warmer takes couple hour a ‘pause’ when it hits that limit?

I have made a Trello ticket on our internal board about this bug, and will investigate it. Can’t give any info yet. But when I have something to say, I will respond to this thread.

@identiden About cache miss:

Maybe could you share your site URL and I will take a look? You can do it here or to our email: [email protected]

So in simple terms, what our plugin does: it visits your pages statically, the same way as simple ‘curl’ command would do this + some extra headers (like User Agent etc).

And why cache does not get created on page visit: it’s up to your cache solution mainly. We can’t debug it.

But I can take a quick look at your site to potentially find some insights.

There is no extra header added with this plugin, right? 

Yes.

But if the cache is created, then the reponse headers usually have it mentioned, from your cache solution. For example, for cloudflare, it would be “cf-cache-status: HIT” (have the cache) or “cf-cache-status: MISS” (no cache).

We have a support in this plugin for this header. See the last column on the screenshot.

But maybe the headers of your cache solution we do not support. This is why I would like to take a look at your site ??

Hi, thank you for the in-depth answers!

I will provide all the screenshots and info via e-mail in a couple moments. I just checked today, and for some reason today a had a cache: bkd header (it’s a LS header for cached on LS, but not on Quic.CDN(when CDN is enabled)) which means the cache warmer did warm the cache! Not sure why now it did work, but I will monitor it for a while and see if I have any issues with it again.

Update. I was wrong about the x-litespeed-cache: bkd header coming from the cache warmer, it was ‘bkd’ since the visit-made cache was removed from the CDN PoP after 24 hours.

So in my case the cache crawler is unfortunately still not creating a cache copy on my Litespeed server. I’ve send all the website info to your e-mail @tmmtechnology. I would really appreciate if you could take a look!

Resolved, all works perfect now. For anyone who uses LSCache and has webp images on, make sure you add Accept: image/webp to ‘Additional Request Headers’.

Also, if anyone with LSCache has the problem when clicking “Start a new warmup” but it doesn’t start/stops after 1 second, make sure your Object Cache is working or try to disable it.