[Zope] Zope fine tuning HOW-TO / Zope Performance

Tony Rossignol tonyr@ep.newtimes.com
Mon, 17 Apr 2000 08:56:52 -0700


Itamar Shtull-Trauring wrote:
> 
> Switching to FastCGI/whatever and tuning the webserver should be the last
> thing you do.

I do not agree here.  If you are looking to optomise your serving
environment tuning Zope extends beyond just tuning zope.

If you want to have a fast serving enviroment splitting the work between
Zope and your basic webserver (we use Apache) is the way to go.  Let
Apache (or what ever webserver) do the repetative serving of images, and
pages that don't change often.  This way you free up Zope for doing what
it does best, managing a dynamic serve environment, and rendering
dynamic content.  

We actually use Apache to cache semi-dynamic sections of our site that
may only change once a day as well as images. This way we off load as
much work as possible from Zope; freeing it up to do the work of dynamic
content and site management duties.

Apache w/ mod_rewrite can also afford you the ablity to load balance
between multiple zope backends, and give you a safety margin when one of
the zope backends is down, or restarting.  We actually monitor all our
zope backends and reconfigure which backend servers are available every
15s so as not to overload a zope server that is starting to become
sluggish - this has proved very helpful.




-- 
-------------------------------
tonyr@ep.newtimes.com
Director of Web Technology
New Times, Inc.
-------------------------------