yuppie wrote:
To get rid of the intermediate [0], use
'properties': {KEY: 'props',
CONVERTER: self._convertToUnique},
'entry-local-roles': {KEY: 'elrs', DEFAULT: ((),),
CONVERTER: self._convertToUnique},
In our regular profiles, listFilteredActionsFor belongs to
the top consumers of CPU time.
Recently, I found the main culprit (in CMF 1.4):
It is the completely unnecessary:
if not action in catlist:
In our case, listFilteredActionsFor spends about 70 percent
of its complete time in
yuppie wrote at 2005-4-4 20:59 +0200:
...
2.) I prefer to see the correct import in each file and to use utils
just for the fallback.
But, then you get a nasty try: ... except: in hundred of
files rather than just a single one.
--
Dieter
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dieter Maurer wrote:
Truong Trung Trang wrote at 2005-4-5 10:57 +0700:
...
I'm doing a project of CMS with Zope and Plone. I'd like to understand
clearly the architecture of Zope but I think that's a hard work for me. It
will much easier if I have
--On Dienstag, 5. April 2005 22:29 Uhr +0200 Dieter Maurer
[EMAIL PROTECTED] wrote:
In our case, listFilteredActionsFor spends about 70 percent
of its complete time in the checking of action in catlist.
I did some profiling last week because Limi complained also about
the slowness of the same
On Tuesday 05 April 2005 10:13 pm, Andreas Jung wrote:
--On Dienstag, 5. April 2005 22:29 Uhr +0200 Dieter Maurer
[EMAIL PROTECTED] wrote:
In our case, listFilteredActionsFor spends about 70 percent
of its complete time in the checking of action in catlist.
I did some profiling last week
--On Dienstag, 5. April 2005 21:44 Uhr -0800 Alec Mitchell
[EMAIL PROTECTED] wrote:
sure it all depends on the specific use case. Whatever the case, this
check is almost certainly unnecessary, whereas the condition checks are
unavoidable and difficult to optimize.
If the check should be
