Skip to content

LSCache Configuration Without Plugins

What is LSCache?

LiteSpeed Cache (also called LSCache) is LiteSpeed's more efficient and highly customizable answer to Apache mod_cache and Varnish.

LSCache is built from the ground up and integrated into all LiteSpeed server products. It can:

  • dramatically speed up dynamic website content (like PHP pages)
  • provide more efficient handling of static content (like images)
  • reduce server load

Understanding Caching

If you are new to website caching, allow us to demystify a few basic concepts.

What is Caching?

Generally speaking, a cache is a mechanism for storing data in such a way that it is easier or faster to retrieve than the original source.

Web application sites consist of dynamic pages that are built with PHP or some other method. The pages of these sites don’t exist anywhere in the file system; they are constructed on-demand by the web app, and then served to the visitor as HTML. Generating these dynamic pages can be resource-intensive and slow.

There are actually several types of caches. LSCache is a "page cache." A page cache's job is to take this dynamically generated web page, and store it as a static HTML snapshot. That way, the next time the page is requested by a visitor, the snapshot can be served immediately. Serving a snapshot is much faster and uses far fewer resources than generating the page dynamically does.

How does LSCache Work?

Imagine you have an uncached page.

A visitor requests that page, and a few things happen:

  • LiteSpeed looks for the page among its stored cache objects and does not find it
  • LiteSpeed returns a "cache miss"
  • The web app dynamically generates a static HTML page while the visitor waits
  • LiteSpeed serves the static HTML page to the visitor
  • LiteSpeed stores the static HTML page as a cache object for later use

A few minutes later, another visitor requests that same page. Here's what happens:

  • LiteSpeed looks for the page among its stored cache objects and finds it
  • LiteSpeed returns a "cache hit"
  • LiteSpeed immediately serves the static HTML page to the visitor

Notice how the inefficient web app is not in the picture at all once the page has been cached? From this point on, until the cache object expires, any visitors who request that page will not have to wait around for the web app.

You can see why caching is good for your visitors, and good for your server load!

Warning

If there is a plugin available for your application, we strongly recommend you use it. There are significant advantages to a plugin, that you cannot get with simple rewrite rules.

If there is no plugin available, you can still use LSCache with your web applications, as long as you meet the server requirements.

Server-Level Prerequisites

Obtain a LiteSpeed Web Server

You will either need LiteSpeed-powered hosting, or one of the following LiteSpeed server products in order to use LSCache:

Install, Configure and Use LSCache

Once you've gotten your web server up and running, you will need to configure the cache root and cache policies, and then set up the rewrite rules that control LSCache's behavior.

Our Installation and Configuration section will get you going.

Additional Support

Community Support

If you've explored our documentation and still have questions, you can find assistance from other LiteSpeed users through our Community Support forums:

Official LiteSpeed Support

To be assisted by a LiteSpeed support technician, you can submit a support ticket from the LiteSpeed website's client area or by emailing support@litespeedtech.com.

Note

We're happy to provide a level of free support for all LiteSpeed products and offer guidance where documentation may fall short. However, we are unable to offer general sysadmin support or hands-on assistance.

Should you require individualized configuration support or hands-on assistance with our products, you can order additional services from the LiteSpeed store.

Thank you for choosing LiteSpeed!

Feedback

Do you have some thoughts about this documentation site? Join our GoLiteSpeed Slack, drop by the #documentation channel, and let us know what you think!