[egenix-users] mxODBC and Python interpreter lock

Tommi Auvinen tommi.auvinen at wicom.com
Fri Feb 21 10:18:40 CET 2003


Hello.

 

There are quite many calls to Windows ODBC library (mxODBC for Python
1.5) that are not freeing the Python lock (for performance reasons, I
guess), and now I have a strong feeling that one or more of those call
do access (in some special cases?) the SQL Server, and if the SQL Server
is _really_ occupied (in fact, other instance of SQL Server hogged it
all) the Python interpreter is locked for a long time. 150 msec lock is
the best I have managed to reproduce in my tests, but in "real life"
there are some cases where the locking time has been tens of seconds.

 

Is there any risk in compiling my own version where all the calls to
ODBC driver API do release the lock (so is performance the only reason
not to free the lock always, or are there other caveats)? 

 

R:TAU

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: /mailman-archives/egenix-users/attachments/20030221/d9b2590b/attachment-0139.htm


More information about the egenix-users mailing list