Re: Hooking persistent.Persistent.__setstate__ was Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-08 Thread Manuel Vazquez Acosta
Alan Runyan wrote: - Customer has software on a remote machine. They are seeing unnecessary transaction commits. Just like the guy 'Analyzing a ZODB'. I'm that guy ;). BTW, we have related those unnecessary commits to CMFQuestions, an old plone product now superseded by PloneSurveys...

Re: Hooking persistent.Persistent.__setstate__ was Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-06 Thread Adam GROSZER
Hello Alan, Sunday, April 6, 2008, 12:30:21 AM, you wrote: AR Question: Is it possible for ZODB 3.9 to have a pure python AR implementation of persistent.Persistent? Maybe this would be a good AR ZODB GSOC project? That would give some help to the Zope 3 components on Jython project too ;-)

Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-06 Thread Dieter Maurer
Manuel Vazquez Acosta wrote at 2008-4-5 11:49 -0400: ... I wonder if there's a way to actually see what objects (or object types) are modified by those transactions. So I can go directly to the source of the (surely innecesary) transaction. The ZODB utility fsdump generates a human readable view

Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-05 Thread Jim Fulton
On Apr 5, 2008, at 11:49 AM, Manuel Vazquez Acosta wrote: Hi all, Recently I was appointed to improve a Plone's performance, and I have the following issue: I see too many transactions made by the anonymous user. I can reproduce this behaviour: just watching the home page produces a

Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-05 Thread Manuel Vazquez Acosta
In a development environment, set a breakpoint (e.g. add import pdb; pdb.set_trace() in ZODB.Connection.Connection.register. You'll be able to see exactly what is causing object changes. I recommend doing this in the zope debugger, which makes it easy to run one request at a time. Dear

Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-05 Thread Jim Fulton
On Apr 5, 2008, at 12:09 PM, Manuel Vazquez Acosta wrote: In a development environment, set a breakpoint (e.g. add import pdb; pdb.set_trace() in ZODB.Connection.Connection.register. You'll be able to see exactly what is causing object changes. I recommend doing this in the zope debugger,

Hooking persistent.Persistent.__setstate__ was Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-05 Thread Alan Runyan
Here is something more ZODB and less Zope related (kinda). I was talking with Benji a few weeks ago about a problem that should be easy to debug but was not. Here is the scenerio: - Customer has software on a remote machine. They are seeing unnecessary transaction commits. Just like the

Hooking persistent.Persistent.__setstate__ was Re: [ZODB-Dev] Analyzing a ZODB.

2008-04-05 Thread Alan Runyan
Here is something more ZODB and less Zope related (kinda). I was talking with Benji a few weeks ago about a problem that should be easy to debug but was not. Here is the scenerio: - Customer has software on a remote machine. They are seeing unnecessary transaction commits. Just like the