[ZODB-Dev] Commit Progress Indictor
Chris S
chrisspen at gmail.com
Fri Aug 25 10:23:44 EDT 2006
On 8/16/06, Jim Fulton <jim at zope.com> wrote:
>
> On Aug 16, 2006, at 5:13 AM, Adam Groszer wrote:
>
> > Hello Andreas,
> >
> > Yep, you're right :-)
> > Are there any hooks in ZODB to support that or that should be a major
> > overhaul?
>
> There are no hooks. It would probably not be a major overhaul,
> however, it would probably require changes at multiple layers and I'd
> be concerned about introducing a performance hit.
>
> Why is this needed? Normally, commiting a transaction doesn't take
> enough time to make this worthwhile, IMO. IN the small GUI app in
> question, are there huge transactions for which this would matter?
> Have long commit times been found to be a problem?
You're right, I suppose there really isn't a need. I was originally
performing a large batch operation and then commiting the one large
transaction, when I should just commit smaller transactions more
often.
On a related note, is there any way to track the progress of db.pack()?
Chris
More information about the ZODB-Dev
mailing list