Automatic cache priming

Hi @philbee,

It’s not in the cache yet, but we do intend to add it, hopefully by next release.

Cheers,
Kevin

Yay!

Hello!

I am very interested in this aswell.
A couple of questions:
– do you have an approximate ETA on this?
– will it be sitemap based and, if so, will it be able to parse sitemap indexes that contain partial XML sitemap themselves?
– will it prime teh cache immediatly after purging regardless of server load or will it be opportunistic?

Thanks!

hi, is there a public roadmap for LS Cache development?

Hi @hlsg

1. No ETA. It is the feature that we are currently working on, however, so it shouldn’t be too long.
2. We will be using our own form of sitemap. I’ll get back to you later on the second question regarding parsing.
3. We plan on having multiple ways to initialize priming. Since the plugin was tailor made to work with LiteSpeed servers, we have the advantage of telling the server when we’re trying to prime the cache. One advantage is that normal users can still be served from cache while we’re priming it in the background. We will probably also have ways to initiate a priming immediately, if desired.

Cheers,
Kevin

• This reply was modified 8 years ago by LiteSpeed Technologies.

Hi @bogdan101083

No public map. The anticipated big feature for 1.0.15 is this automatic cache priming. After that, we anticipate releasing 1.1, maybe at the same time (as a non-stable availability). 1.1 will feature ESI, which can greatly increase the number of pages that we can cache.

After that, it’ll primarily be bug fixes and user requests for features.

Cheers,
Kevin

Hello,

Has this been pushed to a later version than 1.0.15?

Thanks!

Hi @hlsg

No, unfortunately not. We were looking to add it for this release, but it required quite a bit of code overhaul, so we decided to release a version fixing various issues that some people encountered.

The primer code is implemented already, we just need to go through the plugin code to make sure that everything is as optimized as possible.

Sorry for any inconvenience that this may have caused.

Cheers,
Kevin

Thanks for teh reply. No inconvenince. Just wanted to confirm that you didn’t just miss it in the changelog. So we should expect this in 1.0.16?

Yes! that’s the plan. We may release a bugfix version like 1.0.15.1, but priming is a big feature and that won’t be until 1.0.16.

Hello,

Your information on teh new crawler is a bit cryptic at best. I presume this is what it handles. My main concearn is that i woudl like to access the actual sitemap used to see if it is crawling what it’s supposed to.
Also, my questions from an abose post stand:
– will it be sitemap based and, if so, will it be able to parse sitemap indexes that contain partial XML sitemap themselves?
– will it prime the cache immediatly after purging regardless of server load or will it be opportunistic?

I gusee i still wish i could use my own sitemap.

Thnak you!

Hi hlsg,

The crawler in v1.1.0 didn’t support customized sitemap yet. We are planning to add this feature.

Currently crawler only is triggered by cron or manually run button. Running crawler immediately after purge all is a good idea. We will add it to future release.

Cheers