Significant advantages to better integrate with LScache

  • Resolved Pk

    (@paulka)


    2 years, 8 months ago

    From the page https://docs.litespeedtech.com/lscache/lscwp/api/

    “Any WordPress plugin that populates front-end content that can be publicly cached should work with LSCache.

    However, if the plugin needs to update some data, and the cache does not automatically purge the cached page, you may be required to write an integration script to remedy this or invoke LSCWP’s third party plugin integration framework .”

    This post is meant to be a bit of a feature suggestion. After searching the forums learning more and more about web server caching and the differences between disk-caching and app-level caching there are significant advantages of app-level caching. This can be be seen in tffb load times, and is especially effective when used in conjunction with compatible server technology (i.e. litespeed or redis).

    After reading the FAQs and reading all the replies about how to make the two plugins compatible I find my solution lacking. If I choose to forgo the advantage of app-level caching, the move to a new host with litespeed and the benefits of integration are lost.

    Without your plugin dynamic sites on Cloudflare are just not as good. In my opinion you guys have developed the single best cloudflare integration plugin for wordpress.

    But when using the fallback page caching solution we loose all the advantage of the LScaceh plugin app-level cahing. Another example is object caching, we would need to install a 3rd plugin.

    However when we disable the fallback page cache (against your recommendation), and use only LSCache we run into other problems. There are weird fragments of cache kept on Cloudflare and the cart of our WooCommerce store.

    So would there be a possibility of more deeply integrating your plugin with LSCache so the clear cache calls are sync’d? Perhaps there are other advantages or disadvantages, so any comments are greatly appreciated.

    • This topic was modified 2 years, 8 months ago by Pk.
    • This topic was modified 2 years, 8 months ago by Pk.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    First of all you have to understand that in any website there should not be more than one page caching system in place as that will create conflict between who gets to serve the cache.

    When using this plugin you cannot use LS cache for page caching as this is a page caching plugin with handles the whole page cache. Moreover our fallback cache is just a fallback cache for situations where pages are expired or not yet cached in Cloudflare CDN.

    But even in that case, after the first request, Cloudflare will cache the request and will serve from CDN. So, the fallback cache is there just to serve very brief requests before it get cached in Cloudflare.

    Moreover, you can disable fallback cache is you want in that case when a request is not cached in CF CDN yet, the origin server will use PHP to generate the page content and then that content gets cached in Cloudflare.

    For object cache, you can use redis and there are dedicated redis object caching plugin available for WP. But if you like not to serve your cached content from CF CDN and instead want your cached content to be always served via the origin server, you can disable this plugin and use LS Cache.

    The goal of this plugin is to make disk caching just as a fallback as it will mainly be serving content from CDN.

    Thread Starter Pk

    (@paulka)

    Thank you @isaumya for your good explanation ?? I totally agree a website should only use 1 page caching plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Significant advantages to better integrate with LScache’ is closed to new replies.