mediaatwork

ok, thx this is a good one. I have to check, if we can find a way to only “de-cache” the objects which had changed prices …

hmm, beside wp_cache_set and wp_cache_get there is also wp_cache_delete. BUT the flushing is already done, and now we need to warm-up the drained objects again …

not really. So the loading the page will prime the PAGE-cache which in turn loads the pods data from cache also then prime the OBEJCT-cache if the data is not already in the cache. Then the page stays in cache for one week (in our setup).

Now we will have our nightly data-job which at the end will flush the object-cache. But the final pages now will stay in the cache and “pinging” the page will still result into a cache-hit in the page-cache.

Now the esi comes into, so once we expire the price-block any subsequent page load will create a cache creation for the esi which in turn also will go to the object-cache and prime it.

But in fact we will produce and much higher traffic on the web-server but warming up the object-cache directly. Currently we think about to warm the cache by calling all pods with changed prices to make this happen.

But the question here was actually to check if a function like the above was already implemented somehow.

best

Carsten

Right, we are using LiteSpeed Cache and NOT W2TC, and this question is NOT about the page cache but the object-cache used by pods! So please do not hitchhike the ticket.

• This reply was modified 1 year, 11 months ago by mediaatwork.

Thx for your reply. I checked the log already but I think we could manage to solve the point for outself. The magic seems to come from the control parameter. So once we set this to ‘public,no-vary’ instead of ‘private,no-vary’ we can use litespeed_purge. No idea where the relation here is, but now we have a working model.

best