[Zope-CMF] Plong/CMF lack of speed?
Grégoire Weber
gregoire.weber@switzerland.org
Mon, 09 Sep 2002 14:03:32 +0200
Hi all,
As Plone page delivery speed worried me also, I've done some tests
which I would share.
Have a look at the results. They may give you some interesting
hints!
All tests I made were done with the unchanged plone home page
and a my stuff folder_contents page served by Zope and loaded
from the local filesystem by Mozilla and Lynx (text browser).
The first load after starting zope was not measured. Zope runs
in debug mode (-D option).
Home page measurements (total of 3 images and 6 css files loaded):
(1) Mozilla from zope on localhost, Javascript on: 7.0 seconds
(2) Mozilla from zope on localhost, Javascript off: 6.8 seconds
(3) Lynx from zope on localhost (no images, no js): 1.3 seconds
(4) Mozilla from local file, Javascript on: 2.3 seconds
(5) Mozilla from local file, Javascript off: 2.0 seconds
(6) Lynx from local file (no images, no js): not measurable
folder_contents page measurements (6 items in the list, total of
18 images and 6 css files loaded):
(7) Mozilla from zope on localhost, Javascript on: 11.5 seconds
(8) Mozilla from zope on localhost, Javascript off: 11.5 seconds
(9) Lynx from zope on localhost (no images, no js): 1.8 seconds
(10) Mozilla from local file, Javascript on: 1.9 seconds
(11) Mozilla from local file, Javascript off: 1.8 seconds
(12) Lynx from local file (no images, no js): not measurable
Interpretation:
- ZPT performance is not the bottle neck (IMHO) (3) and (9).
- Mozilla rendering takes about 2 seconds (4)and (10).
- Intensive use of js seems not to be a real problem (1)&(2),
(4)&(5), (7)&(8) and (10)&(11)
- Due to the complexity of the Plone GUI takes more time to
render on the client side than rendering the the ZPT file on
server side (on my machine, this gets even worse on slower
machines).
- The unnecessary reload of static parts of the page (images
and css files) slows down overall page delivery drastically.
Recommandations (not really new ones :-):
- Caching: Have a look at caching parameters of static content
(enable client side caching and work with a proxy cache)
- Complexity: reduce the complexity of the pages delivered (at
least of pages for anonymous users for use with ancient
computers)
- ZPT tweaking: I would not recommend tweaking ZPT pages to
generate speed ups in the region of tenth of seconds.
Comments?
Soft- and Hardware:
Zope 2.5.1, CMF 1.3, Plone 1.0alpha2, Mozilla 1.0, Lynx 2.8.3, Win2k,
900MHz Athlon, 768 Mbyte RAM
Greetings, Greg
At 00:09 09.09.2002 +0200, Johan Carlsson [Torped] wrote:
>Hi,
>I just installed the latest Plong release (windows) and I was struck
>by fact that feels so slow (an most probably there for are, unless if
>there is something really stinky going on? (I run a rather old laptop which
>is excellent on detecting slow softwares :-)
>
>My question is if this is something someone else has noticed and=
investigated before me?
>In that case, what's the probable cause?
>Is it Plone that is slower than regular or does this have anything
>to do with CMF (I usually don't run CMF on this machine so I doesn't
>really have anything to compare Plone to, except from my regular
>Zope sites (which I do run on this machine) which feels significantly=
faster.
>
>I suspicious that it might be the portal_skin __getattr__ that slows things=
down?
>
>My experience of CMF is more of the source code that actually running it.
>(IMHO because the source code is far more interesting than an accusal CMF=
site)
>
>Regards,
>Johan Carlsson
>
>
>_______________________________________________
>Zope-CMF maillist - Zope-CMF@zope.org
>http://lists.zope.org/mailman/listinfo/zope-cmf
>
>See http://collector.zope.org/CMF for bug reports and feature requests
_____________________________________
Grégoire Weber
mailto:gregoire.weber@switzerland.org