Re: Diazo overhead?

I think there was some mention at the conference of an overhead

from using "*" in some Diazo rules. Would anyone care to expand on
that?

Daniel

On 05/11/14 22:53, Martin Aspeli wrote:

On 5 November 2014 19:36, Sean Upton
<[email protected] >
wrote:

Diazo
newbie question:

What's the typical overhead for Diazo to run a transform
on a very

typical page in Plone? I have not been able to determine
this, and

have not yet needed to invest the effort to profile it
against some

non-trivial theme.

Pretty low. It's pretty well optimised (unless you have
very complex or very open-ended XPath queries).

Probably much less than whatever else you're doing on
the page. But you always need to benchmark your particular
use case and try not to optimise prematurely.

Â

In trying to understand how plone.app.theming (and

plone.transformchain) works, AFIACT it looks like there is
no

caching/memoization of a transform result, even if the
response body

prior to transform is byte-for-byte identical to a
previously

transformed request in the same instance (not in
development mode;

only the transforms themselves are cached, not the
result).

No, because there's not been a need to optimise that
bit yet. Generally, if this were the case, you'd cache the
page anyway and/or pass a 304 response so the request
would never even hit Plone.

Â

Martin

------------------------------------------------------------------------------

_______________________________________________
Plone-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-users

--

Daniel Jowett

Jowett Enterprises Ltd

Tel: 0333 3 553 773

Mobile: 07870 667 126

[email protected]

www.jowettenterprises.com

------------------------------------------------------------------------------

_______________________________________________
Plone-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-users