Hector, Are you doing a lot of href(sub requests) in your rules to pull in different content?
I can imagine that can really slow down performance. On Thu, Mar 15, 2012 at 7:47 PM, Héctor Velarde <[email protected]> wrote: > On 15/03/12 06:11, Laurence Rowe wrote: >> >> plone.app.theming.transform.transformIterable should be called only once >> per >> request, I would suggest working out why is being called so many times. > > > no, plone.app.theming.transform.transformIterable is called on _every_ > request; it just exits early if the content isn't Diazo's business, but > that's another story. > > after more profiling I have found that all the delay happens inside this > method when the rules are applied and it's very different depending on what > kind of page is being processed; it's becoming critical on content creation > (30s vs 1s with no Diazo theme applied). > > we're right now working on a complete refactoring of the rules, but I think > it's important to give more information to theme developers about how > complex sites performance could be affected by Diazo and what are the best > practices do deal with this. > > as I mentioned before, this is extremely important on the content creation > side because (and correct me if I'm wrong) no caching can be applied there > and the delay occurs all the time. > > best regards > > > _______________________________________________ > Setup mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/plone-setup > _______________________________________________ Setup mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-setup
