[Zope] Improving CMS Performance: Help Needed
Scott Burton
mrzope@hotmail.com
Thu, 25 Jul 2002 15:34:15 +0000
<html><div style='background-color:'><DIV>
<P>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: <A href="http://www.zope.org/Members/richard/CallProfiler/news">http://www.zope.org/Members/richard/CallProfiler/news</A>. And <A href="http://www.zope.org/Members/mcdonc/HowTos/DEBUG-LOG">http://www.zope.org/Members/mcdonc/HowTos/DEBUG-LOG</A> This will show you where and what is slow in your app.</P>
<P><BR>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?</P>
<P>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.</P>
<P>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.</P>
<P> </P>
<P>Scott Burton<BR></P></DIV>
<DIV></DIV>
<DIV></DIV>>From: Klaus Herrmann <KLAUS.HERRMANN@GOELZ.COM>
<DIV></DIV>>To: zope@zope.org
<DIV></DIV>>Subject: [Zope] Improving CMS Performance: Help Needed
<DIV></DIV>>Date: 25 Jul 2002 16:02:47 +0300
<DIV></DIV>>
<DIV></DIV>>Hi Folks!
<DIV></DIV>>
<DIV></DIV>>We have developed a nice CMS ontop of Zope, that dynamically renders
<DIV></DIV>>pages (with DTML and a python Product) out of special Components (e.g.
<DIV></DIV>>text blocks and headlines). The only bad thing is: The Performance
<DIV></DIV>>really sucks.
<DIV></DIV>>
<DIV></DIV>>I experienced that Zope is able to serve ~50 REQUESTs per Second on a
<DIV></DIV>>small static page (where apache does 1500-2200), but under heavy DTML-
<DIV></DIV>>and Python usage, Zope will only be able to serve ~ 0,5 - 5 pages per
<DIV></DIV>>second (depending on how big the page is and how complicated its python
<DIV></DIV>>logic).
<DIV></DIV>>
<DIV></DIV>>Well, i am aware of the fact that cache managers are able to
<DIV></DIV>>dramatically improve performance, but in most cases, our content and
<DIV></DIV>>pages are just too dynamic for the application to work w/ enabled cache
<DIV></DIV>>(RAM or HTTP or ProxyPass).
<DIV></DIV>>
<DIV></DIV>>Does anyone know some hints how to get more performance out of zope? Any
<DIV></DIV>>common Python / DTML routines that cost way too much time? Any
<DIV></DIV>>experiances in improving Zope's speed?
<DIV></DIV>>
<DIV></DIV>>System is Zope-2.5.1 on FreeBSD-4-Stable and Python 2.1.3.
<DIV></DIV>>Hardware: Tested on Xeon / 1,26GHz / 512MB RAM and Athlon / 850MHz /
<DIV></DIV>>256MB RAM
<DIV></DIV>>
<DIV></DIV>>Thanks in advance!
<DIV></DIV>>
<DIV></DIV>>regards,
<DIV></DIV>> Klaus
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>--
<DIV></DIV>>Goelz & Schwarz GmbH
<DIV></DIV>>Waltherstrasse 29, 80337 Muenchen, Germany
<DIV></DIV>>phone: + 49 - (0)89 / 54 46 70 - 0
<DIV></DIV>>fax: +49 - (0)89 / 54 46 70 - 10
<DIV></DIV>>e-mail: klaus.herrmann@goelz.com
<DIV></DIV>>web: http://www.goelz.com
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>_______________________________________________
<DIV></DIV>>Zope maillist - Zope@zope.org
<DIV></DIV>>http://lists.zope.org/mailman/listinfo/zope
<DIV></DIV>>** No cross posts or HTML encoding! **
<DIV></DIV>>(Related lists -
<DIV></DIV>> http://lists.zope.org/mailman/listinfo/zope-announce
<DIV></DIV>> http://lists.zope.org/mailman/listinfo/zope-dev )
<DIV></DIV></div><br clear=all><hr>MSN Photos is the easiest way to share and print your photos: <a href='http://g.msn.com/1HM1ENUS/c156??PI=44364'>Click Here</a><br></html>