Accessing /sitemap also seems to do this. Not sure how this can be disabled.
On Wednesday 14 March 2012 09:04 PM, Laurence Rowe wrote:
hvelarde wrote
during the deployment of a new site using Diazo we have found huge
performance problems causing delays of more than 25 seconds on each page
loaded.
these problems are more evident, and intolerable, for logged in users
accessing the site to add content.
a quick review using some profiling tool showed us where the problem is:
64 calls to transformIterable() [1] causing delays of 0.374 seconds each
one.
we obviously need to rethink the theme to reduce the number of
transformations, but I would like to listen to other people's advice:
have you ever found such performance issues when using Diazo on your
deployments?
what's the best approach for using Diazo with complex themes? WSGI or
nginx? [2]
best regards
[1]
https://github.com/plone/plone.app.theming/blob/master/src/plone/app/theming/transform.py#L200
[2] http://docs.diazo.org/en/latest/deployment.html
--
Héctor Velarde
I've certainly never observed anything like this. Martin's performance tests
from a few years ago showed that performing the transform in process was
faster than doing so in a proxy. For Plone, plone.app.theming is the
recommended deployment mechanism.
There's not really enough information here to know why this might be
happening. If you can isolate it and turn it into something I can easily
reproduce in a standard plone.app.theming build I'll take a look.
Laurence
--
View this message in context:
http://plone.293351.n2.nabble.com/huge-performance-issues-using-Diazo-tp7372056p7372162.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.
_______________________________________________
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
