Hi.
I tried to analyze the overhead of changing content in Plone a bit. It
turns out we write back a lot of persistent objects to the database,
even tough the actual values of these objects haven't changed.
Digging deeper I tried to understand what happens here:
1. persistent.__setattr__ will
On 4 May 2011 11:53, Hanno Schlichting ha...@hannosch.eu wrote:
I tried to analyze the overhead of changing content in Plone a bit. It
turns out we write back a lot of persistent objects to the database,
even tough the actual values of these objects haven't changed.
How about identifying the
On 4 May 2011 10:53, Hanno Schlichting ha...@hannosch.eu wrote:
Hi.
I tried to analyze the overhead of changing content in Plone a bit. It
turns out we write back a lot of persistent objects to the database,
even tough the actual values of these objects haven't changed.
Digging deeper I
On Wed, May 4, 2011 at 1:09 PM, Laurence Rowe l...@lrowe.co.uk wrote:
Persistent objects are also used as a cache and in that case code
relies on an object being invalidated to ensure its _v_ attributes are
cleared. Comparing at the pickle level would break these caches.
So you would expect
