Alexander Limi wrote:
It seems the portlets stuff is what is making it slower (more about that
below), along with globalize.
...
So for logged-in, "globalize" and the versioning stuff seems to be the
two biggest offenders by an order of magnitude, and seem to both take
about the same amount
Hi Philipp,
I wish we could come up with a way to to get rid of the globalize stuff
sanely. It's an instane overkill to compute this magnitude of values for
each template, just because a few templates simply "expect" stuff to be
available. Not to mention that it encourages bad coding practices f
Martin Aspeli wrote:
I wish we could come up with a way to to get rid of the globalize stuff
sanely. It's an instane overkill to compute this magnitude of values for
each template, just because a few templates simply "expect" stuff to be
available. Not to mention that it encourages bad coding pra
Hi Philipp,
> - some things make sense to have globally available - portal_url
> possibly being one of them. Having to re-compute it each time
> (getToolByName(self, 'portal_url').getPortalPath()) is annoying
Right. I never said you should have to do that. However, this doesn't
mean they have t
On Nov 14, 2006, at 3:22 PM, Alexander Limi wrote:
I'm tempted to move all this stuff to the History (Versioning) tab,
so you can find it when you need it.
+1 (for what it's worth...)
___
Framework-Team mailing list
Framework-Team@lists.plone.org
h
Martin Aspeli wrote:
> - some things make sense to have globally available - portal_url
> possibly being one of them. Having to re-compute it each time
> (getToolByName(self, 'portal_url').getPortalPath()) is annoying
Right. I never said you should have to do that. However, this doesn't
mean the
You mentioned the thread local idea. That might work. I think we should
also investigate memcached. See Tres's mcdutils package, for example:
http://agendaless.com/Members/tseaver/software/mcdutils. It's important
to note that this cache is absolutely request-specific. It must be
invalidated after
Sidnei da Silva wrote:
You mentioned the thread local idea. That might work. I think we should
also investigate memcached. See Tres's mcdutils package, for example:
http://agendaless.com/Members/tseaver/software/mcdutils. It's important
to note that this cache is absolutely request-specific. It m
On 11/15/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
Cool. I have two problems with this, though:
* the underscore clearly indicates the "privateness" of the _hold
method. In fact, _hold isn't part of the official Request API, I guess
(if there even is such a thing...)
* this doesn
Sidnei da Silva wrote:
On 11/15/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
Cool. I have two problems with this, though:
* the underscore clearly indicates the "privateness" of the _hold
method. In fact, _hold isn't part of the official Request API, I guess
(if there even is such a
(Just so it's recorded on the list)
-- Forwarded message --
From: Philipp von Weitershausen <[EMAIL PROTECTED]>
Date: Nov 15, 2006 1:15 PM
Subject: Re: [Framework-Team] Re: Some preliminary Plone 3.0 profiling results
To: Sidnei da Silva <[EMAIL PROTECTED]>
Sidnei da Silva wrote
11 matches
Mail list logo
