Here are a few things to consider.... #1 Where are your images being served from? If from Zope, you should cache all of the images in the website. #2 What particular areas of the site or actions are slow? If it takes a long time to do one particular thing, then see if you could optimize a script. Some simple things are often the cause of slow performance in a script. #3 What is the Zope process taking up in memory and CPU usage? #4 Run profiling see: http://www.zope.org/Members/richard/CallProfiler/news. And http://www.zope.org/Members/mcdonc/HowTos/DEBUG-LOG This will show you where and what is slow in your app.


You should also consider caching the header and footer or commonly used html-parts of your pages that aren't dynamic. You did set it up that way right?

Also... Are you using the ZODB to store your content or RDBMS? If you are using something like MySQL you might have a problem with your sql or database setup.

All-in-all there are many things that can cause poor performance, not just in Zope but in any dynamic webserver. I have seen Zope endure some serious traffic running dynamic sites on a a little box you wouldn't even consider using as a desktop machine with no performance problems.

 

Scott Burton

>From: Klaus Herrmann
>To: zope@zope.org
>Subject: [Zope] Improving CMS Performance: Help Needed
>Date: 25 Jul 2002 16:02:47 +0300
>
>Hi Folks!
>
>We have developed a nice CMS ontop of Zope, that dynamically renders
>pages (with DTML and a python Product) out of special Components (e.g.
>text blocks and headlines). The only bad thing is: The Performance
>really sucks.
>
>I experienced that Zope is able to serve ~50 REQUESTs per Second on a
>small static page (where apache does 1500-2200), but under heavy DTML-
>and Python usage, Zope will only be able to serve ~ 0,5 - 5 pages per
>second (depending on how big the page is and how complicated its python
>logic).
>
>Well, i am aware of the fact that cache managers are able to
>dramatically improve performance, but in most cases, our content and
>pages are just too dynamic for the application to work w/ enabled cache
>(RAM or HTTP or ProxyPass).
>
>Does anyone know some hints how to get more performance out of zope? Any
>common Python / DTML routines that cost way too much time? Any
>experiances in improving Zope's speed?
>
>System is Zope-2.5.1 on FreeBSD-4-Stable and Python 2.1.3.
>Hardware: Tested on Xeon / 1,26GHz / 512MB RAM and Athlon / 850MHz /
>256MB RAM
>
>Thanks in advance!
>
>regards,
> Klaus
>
>
>--
>Goelz & Schwarz GmbH
>Waltherstrasse 29, 80337 Muenchen, Germany
>phone: + 49 - (0)89 / 54 46 70 - 0
>fax: +49 - (0)89 / 54 46 70 - 10
>e-mail: klaus.herrmann@goelz.com
>web: http://www.goelz.com
>
>
>
>_______________________________________________
>Zope maillist - Zope@zope.org
>http://lists.zope.org/mailman/listinfo/zope
>** No cross posts or HTML encoding! **
>(Related lists -
> http://lists.zope.org/mailman/listinfo/zope-announce
> http://lists.zope.org/mailman/listinfo/zope-dev )


MSN Photos is the easiest way to share and print your photos: Click Here