[Zope-CMF] Re: Plone Speed
alan runyan
alan runyan" <runyaga@runyaga.com
Wed, 15 May 2002 10:55:48 -0500
>> *I* believe the "smoking gun" lies elsewhere (e.g., inside the actions
tool).
if in custom you create a main_template that is only
<html metal:define-macro="master">
<body metal:define-slot="main">
We will fill this with content.
</body>
</html>
and a document_view of
<html metal:use-macro="here/main_template/macros/master">
<body metal:fill-slot="main" tal:content="structure here/CookedBody">
The 'text' contents for a document.
</body>
</html>
if you have these in your 'custom' folder, which is at the head of the
skinpaths and run ab on it.
You get a marginal difference between that and my previous ab results. Is
the portal_actions tool
'calculating anything' when we do not call it?
Here is a quick ab -n 100 -c 2 to the index_html Document object sitting in
a default Plone site with the above main_template/document_view in the
custom folder. same hardware/software. 350Mhz machine; CMF1.3b1, Zope2.5.1
Concurrency Level: 2
Time taken for tests: 7.721 seconds
Complete requests: 100
Failed requests: 0
Broken pipe errors: 0
Total transferred: 139500 bytes
HTML transferred: 116500 bytes
Requests per second: 12.95 [#/sec] (mean)
Time per request: 154.42 [ms] (mean)
Time per request: 77.21 [ms] (mean, across all concurrent requests)
Transfer rate: 18.07 [Kbytes/sec] received
Connnection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 1.0 0 11
Processing: 74 153 40.6 153 368
Waiting: 74 152 40.0 153 357
Total: 74 153 40.6 153 370
Here is the /QuickStart page.
Concurrency Level: 2
Time taken for tests: 6.426 seconds
Complete requests: 100
Failed requests: 0
Broken pipe errors: 0
Total transferred: 327900 bytes
HTML transferred: 299900 bytes
Requests per second: 15.56 [#/sec] (mean)
Time per request: 128.52 [ms] (mean)
Time per request: 64.26 [ms] (mean, across all concurrent requests)
Transfer rate: 51.03 [Kbytes/sec] received
Connnection Times (ms)
min mean[+/-sd] median max
Connect: 0 1 6.4 0 64
Processing: 61 126 46.8 123 324
Waiting: 11 125 48.0 122 324
Total: 61 127 47.7 123 324
and the /Examples/index_html:
Concurrency Level: 2
Time taken for tests: 5.824 seconds
Complete requests: 100
Failed requests: 0
Broken pipe errors: 0
Total transferred: 137900 bytes
HTML transferred: 114900 bytes
Requests per second: 17.17 [#/sec] (mean)
Time per request: 116.48 [ms] (mean)
Time per request: 58.24 [ms] (mean, across all concurrent requests)
Transfer rate: 23.68 [Kbytes/sec] received
Connnection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 2
Processing: 55 114 48.4 97 379
Waiting: 55 114 48.4 97 379
Total: 55 114 48.4 97 379
maybe these base line ab runs give you more to decide on just how slow my
hardware is.
anyway. I'm not sure what the smoking gun is. sometimes I've received
really bizarre performance
until I reindexed my catalogs. I just put a script in the custom that does
REQUEST=context.REQUEST
return REQUEST.PARENTS and called it from document_view. there was
essentially no speed difference.
12.29req/sec (return REQUEST.PARENTS) to 12.37req/sec (return 'nothing').
this is also benchmarking using
the shotgun approach.
Q: are macros compiled and are they 'expanded' each time? or once they are
expanded thats usually the last time they need to be expanded?
~runyaga
>
> Tres.
> --
> ===============================================================
> Tres Seaver tseaver@zope.com
> Zope Corporation "Zope Dealers" http://www.zope.com
>
>
>
> _______________________________________________
> Zope-CMF maillist - Zope-CMF@zope.org
> http://lists.zope.org/mailman/listinfo/zope-cmf
>
> See http://www.zope.org/Products/PTK/Tracker for bug reports and feature
requests
>