1. Home
  2. Technical Support
  3. Introduction to LiteSpeed Cache

Introduction to LiteSpeed Cache

For our performance hosting services we have configured LiteSpeed Cache, now avaliable for the use of our clients as a complimentary service.

LiteSpeed Cache can be configured/managed without a need of prior technical knowledge, making it simple to configure for your website using the provided LiteSpeed Cache plugins. LiteSpeed supports a number of popular web applications such as WordPress, Magento, Craft, Joomla, Drupal and so on. Feel welcome to view their official documentation to find out whether there is a LiteSpeed Cache plugin for your web application.

Cache rules are managed by entries in the .htaccess file so it is not necessary to rely on a plugin to use this service however it would require more in depth knowledge to configure the correct ruleset using this method. If interested, please reference LiteSpeeds no plugin setup guideline.

There are two avaliable cache types when using LiteSpeed Cache;

  1. Public Cache–  designed for website content which is not user specific, this content is changed infrequently and can be served to any site visitor. Keep in mind although content is considered reasonably static, when updating web content, LSCache has inbuilt triggers which will flush stored cache version. For example: LSCache will be triggered to flush cache when any of the following actions are made: edit_post, save_post, deleted_post, deleted_attachment and trashed_post.
  2. Private Cache- designed for user specific content, private cache should be used for areas such as the websites admin area, contact forms, personalised greetings etc. The content served is unique for each user (usually tracked by either IP address or session ID) so always be mindful when identifying areas where private cache is necessary to ensure sensitive data is protected.

Cache storage

Our performance servers each have a partition dedicated to the storage of our clients public cache files, this reduces the disk usage overhead for our clients, while we are able to store public cache files outside of a users home directory, as a security measure private cache files will always be stored within a users home directory. By default private cache files are stored under ~username/lscache.

ESI (Edge Side Includes)

LSCache also supports ESI which is a markup language allowing you to break up a webpage into different cache types. Ultimately using a combination of public and private cache with ESI means you can cache the majority of your web content, greatly accelerating load speeds and in turn improving user experience.

 

 

 

 

Updated on July 4, 2018

Was this article helpful?