Hello Jim, For my small GUI app it happens that commit time is around 10-30 seconds depending on the object count&size. But until now it is not worth doing big changes in ZODB. I can put a fake progress indicator anytime that advances every second a bit and never reaches 100%.
Advertising
Wednesday, August 16, 2006, 1:05:14 PM, you 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? > Jim > -- > Jim Fulton mailto:[EMAIL PROTECTED] Python > Powered! > CTO (540) 361-1714 > http://www.python.org > Zope Corporation http://www.zope.com http://www.zope.org -- Best regards, Adam mailto:[EMAIL PROTECTED] -- Quote of the day: To be intoxicated is to feel sophisticated but not be able to say it. _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
