Christian Boos wrote: > Hello, > > There's a patch I'd like to commit on stable before 0.11.1, but first > I'd like to check if nobody foresees a problem with this, and also if I > could get some testing feedback, particularly from people still > experiencing db timeout errors. > > This patch should improve upon concurrency and reduce the risks for a > timeout while waiting for a db connection, when Trac is used with a > cached svn repository (i.e. probably still the typical situation). > > Up to now for those setups, every request initializes a CachedRepository > object which will only be freed at the end of the request (during > shutdown(tid)). Since a db connection is stored there, that connection > can't go back to the pool even if it's not used and so it cannot be > reused by other requests. > > The proposed patch fixes this. It's done in a backward compatible way, > in case some other vc backends are reusing the CachedRepository. > > It'd be nice if jonas could try it on some heavily used Trac ;-)
The patch has been running on t.e.o for a couple of hours now and everything seems to be working ok. There might also be slightly fewer active database connections now but it's hard to tell since Saturdays are the least busy day of the week anyway. / Jonas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
