Am 09.02.2009 um 18:53 schrieb Tres Seaver:
This is talking directly to Zope (no Varnish / Squid in front?)
Please
post the PythonScript, too.
Yep, this is a local wget talking directly to Zope.
The PythonScript is:
request = context.REQUEST
styles = []
styles.append(getattr(context,
Am 10.02.2009 um 10:16 schrieb Charlie Clark:
Now the profile results:
1) View
4499 function calls (4476 primitive calls) in 0.110 CPU seconds
2) PythonScript
12830 function calls (12786 primitive calls) in 0.154 CPU seconds
I've added an interator which reduces the number of calls:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie Clark wrote:
Am 09.02.2009 um 18:53 schrieb Tres Seaver:
This is talking directly to Zope (no Varnish / Squid in front?)
Please
post the PythonScript, too.
Yep, this is a local wget talking directly to Zope.
The PythonScript is:
Am 10.02.2009 um 14:36 schrieb Tres Seaver:
You could try changing the view to call 'index_html' instead of
'__str__', and see if that helps. If it does, then I think there must
be a RAM cache in play somewhere.
I actually reckon it's an anomaly down to my rather unscientific
testing
Hi,
I've written a very simple view for concactenating resources such as
CSS or Javascript files to reduce the number of http browser requests:
from Products.CMFCore.utils import getToolByName
from Products.CMFDefault.browser.utils import memoize, ViewBase
class Javascript(ViewBase):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie Clark wrote:
Hi,
I've written a very simple view for concactenating resources such as
CSS or Javascript files to reduce the number of http browser requests:
from Products.CMFCore.utils import getToolByName
from
Am 09.02.2009 um 16:10 schrieb Tres Seaver:
Try profiling the two requests and see what looks different.
I thought someone might say that... ;-)
As heavy upstream caching is likely to be used I hope it's not
necessary to optimise this too much. The main advantage is reducing
the number of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie Clark wrote:
Am 09.02.2009 um 16:10 schrieb Tres Seaver:
Try profiling the two requests and see what looks different.
I thought someone might say that... ;-)
As heavy upstream caching is likely to be used I hope it's not
necessary
