Personal tools
You are here: Home → Documentation → Tutorials → Optimizing Plone Performance
Support

Get Help

Join our chat rooms or support forums if you have more specific questions.

Plone Training
Learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.
Find Plone training…
 
Document Actions

Optimizing Plone Performance

This Tutorial applies to: Any version.
This Tutorial is intended for: Server Administrators

This tutorial will show you a simple and effective way to use caching to make your Plone site a production-worthy setup capable of delivering in excess of 100 pages per second given proper hardware. (In progress)

limi

All content on one page (useful for printing, presentation mode etc.)

  1. Introduction, goals and credits What this tutorial does and does not cover, and who's responsible for it.
  2. Common elements to caching A brief explanation about what we are going to set up.
  3. Caching setup using Apache 1.3 How to make the server ready to cache - using Apache 1.3.
  4. Caching setup using Apache 2.0 How to set up the caching using Apache 2.0.
  5. Deciding what to cache What content can be cached, and how do you set it up for an optimal experience?
 
by Alexander Limi — last modified February 12, 2006 - 15:06
Contributors: Alexander Limi, Seb Potter
All content is copyright Plone Foundation and the individual contributors.

Setting allowed proxy domains

Posted by Mikko Ohtamaa at July 31, 2006 - 03:51

By default, Apache 2 blocks proxy requests from every IP. To make mod_proxy work, you need to allow proxy requests from localhost.

Edit /etc/apache2/mods-available/proxy.conf: 

        <Proxy *>
                Order deny,allow
                Deny from all
                #Allow from .your_domain.com
                Allow from mymachine.some.net
        </Proxy>

Allow Plone to cache pages

Posted by Mikko Ohtamaa at July 31, 2006 - 05:12

By default, most dynamic Plone objects, like documents, are not cacheable. One needs to enable caching page templates by editing page template metadata in Zope management interface.

For example, my site front page was Page (ATDocument) and it was not cached until I set cache=HTTPCache for document_view in ZMI.

For more information about caching with Plone, see Plone Book chapter 14: http://www.jazkarta.com/technology/plone/plonebook/ch14.rst

Go to Zope management interface, portal_skins -> plone_content -> document_view. Click Cache tab and set cache to HTTPCache.

Actually, I believe CacheFu fixes this?

Posted by Alexander Limi at September 9, 2007 - 18:37
IIRC, CacheFu sets these headers on content, so things are cacheable.

This tutorial really needs to be updated with current best-practices, though. :)

can this be updated?

Posted by John DeStefano at January 5, 2007 - 16:42
This is a great starting point for caching and performance, but both the tutorial and the chapter in the Plone Book on "Administering and Scaling Plone" have grown a bit outdated: for instance, global_cache_settings has changed and no longer includes Pragma directives in Plone 2.5.1, but the current template _does_ include an Expire directive, which this tutorial claims can be left in but the Plone Book recommends removing.

I'd love to see an updated version of this, in addition to options for enabling caching with RewriteRule directives instead of reverse-proxies.

Versión en Español - Spanish version

Posted by Roberto Allende at September 9, 2007 - 15:49
http://plone.org/countries/conosur/documentacion/tutorial-optimizando-la-performance-de-plone

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by