Evolved Caching Documentation

Using the content below you can find in depth documentation on the setup and usage of Evolved Caching. There is also a quick setup guide to get you up and running with the minimum fuss, and more in depth developer resources which run through how to easily customise your store and Evolved Caching for full functionality on even the most heavily customised stores.

Continue reading below for useful information on how Evolved Caching will benefit performance, and what it will improve on your store.

  1. Quick Setup
  2. Installation
  3. Caching Exclusions
  4. General Options
  5. Cache Storage
  6. User Agents (optional)
  7. Headers (optional)
  8. Caching Key Cookie (optional)
  9. Dynamic Content Display (optional)
  10. Automatic Cache Clearing (optional)
  11. Automatic Cache Warming (optional)
  12. Cache Locking (optional)
  13. Managing Cache Entries (optional)
  14. Licensing
  15. Varnish
  16. Developer Resources

How Evolved Caching will benefit your store

How does Evolved Caching effect performance?

In simple terms Evolved Caching stores the HTML which Magento generates for every page, and then serves this stored HTML the next time that page is viewed. Each time Magento generates HTML for a page many thousands of lines of code are executed (even for simple pages) and this takes a significant amount of time to do.

What Evolved Caching does is store this HTML and then serve it the next time that page is viewed. This means that Magento no longer has to execute the thousands of lines of code to generate the HTML for each page and instead Evolved Caching just serves it's stored HTML. The result is just a very few lines of code being executed giving a very significant boost in performance.

What will Evolved Caching improve on my store?

There are 3 main areas you need to focus on when looking at improving your stores performance, and Evolved Caching (in fact any caching solution including Varnish) will only help in one of these areas. These three areas are:

  1. The hardware your store is running on, so your hosting package. Your hosting is the foundation for your entire store and Magento will only ever run as well as your hosting allows. You should always avoid shared hosting with Magento as the resources just aren't available to run Magento smoothly. A well specced VPS or a private server are both good hosting options for Magento - they will cost more but without this the poor performance of your store will be a major obstacle to getting any sales.
  2. The time it takes for the first request to complete. This is the request for the full page HTML and exactly the request which Evolved Caching improves. Although the server will process many requests for every page it loads, this first request is by far the slowest and most resource intensive. All other requests will just be for assets like images, JS and CSS and will require very minimal processing by the server making then individually very quick to complete.
  3. The number of assets per page. Although a request for a single image, JS or CSS asset is quick to complete if you have many assets, this does have a significant effect on how long it takes for pages to finish loading entirely. You should reduce assets by turning on JS and CSS merging, and reducing the number of images on your pages as mush as possible.

To summarise, Evolved Caching should be implemented for a site running on good hosting, with JS and CSS merging enabled, and with as few images as possible per page. This will give you the greatest performance benefit and allow the store to run as fast as possible for your setup.

For more detailed information on the above read our blog post on speeding up Magento. Also try out our performance profiler for specific information on your stores current performance, and how to improve it.