Thread Starter
mcdeth
(@mcdeth)
One more question, is there a way to manually warm up cache, like using curl or a spider such as screaming frog? This method doesnt work with litespeed for example
-
This reply was modified 10 months ago by
mcdeth.
-
This reply was modified 10 months ago by mcdeth.
Plugin Support
Kush
(@kushnamdev)
Hey @mcdeth,
Thank you for contacting us.
Yes, the plugin is compatible with WPML. For Redis, there is an option inside the plugin which will allow you to purge redis cache when you purge the SPC cache. Will that help with your usecase?
Also, you can warm up cache by using CRON jobs, you will find this option inside the plugin.
Best regards
Thread Starter
mcdeth
(@mcdeth)
Thanks a lot! So I’m keeping litespeed only for CSS/JS optimization and Redis.
Does it make sense to keep ls crawler enabled?
I understand litespeed cache isn’t triggered by curl, but if Super Page Cache does trigger it, then it’ll be cached anyway. So would crawling beforehand actually help, or just add load?
Sounds like a bit of overhead and bloating db with crawler idea, so perhaps better turn off crawler..
2nd question, for warming up we’re looking at Preloader operation? Is there any documentation or information how long does it take to preload x pages?
Thread Starter
mcdeth
(@mcdeth)
Regarding the first question about whether it’s worth keeping the LiteSpeed crawler, I noticed that there’s an intentional cache miss when a user has an item in their cart. In such cases, the LiteSpeed cache takes over. Is there perhaps a way to serve cached pages even to users who already have items in their cart? I don’t mind writing a script to update cart with js if it helps. I dont have mini cart
