[ZCM] [ZC] 1642/ 3 Assign "ZEO responsiveness improvement"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1642 Update (Assign) "ZEO responsiveness improvement"
 Status Accepted, Database/feature+solution medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/1642

==============================================================
= Assign - Entry #3 by tim_one on Aug 3, 2005 3:49 pm

 Status: Pending => Accepted

 Supporters added: tim_one


________________________________________
= Comment - Entry #2 by ajung on Aug 3, 2005 4:19 am

Is this still an open issue for the most current ZODB version?
________________________________________
= Request - Entry #1 by d.maurer on Dec 29, 2004 5:35 am


Uploaded:  "zeo_resp.pat"
 - http://www.zope.org/Collectors/Zope/1642/zeo_resp.pat/view
For huge transactions ZEO spends a long time (in the order of minutes)
in the call to "vote". This makes it irresponsive for other requests,
e.g. probes by monitoring software.

This has been discussed in Dez. 2004 on "zodb-dev" with Jeremy Hylton.


The attached patch (against ZODB 3.2)
lets '_restart' (which causes the long irresponsiveness
periods) execute in a separate thread for huge transactions.


Note that I expect serious problems when an originally delayed operation
results in an exception. If formerly any exceptional case during
execution of the delayed operation including connection close was
handled perfectly, then the execution in a separate thread should
work, too. However, if there were wholes, then formerly
problems simply caused a client disconnected while
now the server may end up not releasing the commit lock.


==============================================================