Document Actions
Introduction, goals and credits
limi
In this tutorial, we will teach you how to cache your Plone site in a good way to get it responsive and fast for anonymous users visiting your site.
The strategy presented is a simple and efficient one, but has some caveats, and is not the magic silver bullet to solve any performance problem you may have. Very often, performance problems in Plone sites are caused by improper setup of Plone or the server it is running on, or badly written third-party products. It's important to know that there are more aspects that have to be taken into consideration when optimizing the performance of a Plone site.
This tutorial aims to do the following:
- Set up a web server in front of Plone that can cache elements that are marked up as being cachable - so they don't hit the Plone instance at all - but are rather served by the web server cache in front of it. This is especially efficient for assets like files, CSS and Javascript, but you can also apply it to entire pages if you need to serve up pages extremely fast.
- Set up a different virtual host with no caching for editor usage.
Credits
The Apache 1.3 setup was originally written up by Seb Potter, and was adapted to the updated Plone and Zope versions by Alexander Limi.
