On Tue, 2004-08-10 at 10:48, Dave Peticolas wrote:
I want to ensure that a connection pool can actually make use of all of its connections simultaneously if it needs to (the performance half of why a connection pool is used in the first place). If adbapi were to ignore the reactor thread counts altogether, for example, it would be pointless to specify a max connections greater than 10 since the reactor won't let you use more than that anyway, the default max thread count being 10 atm.
Aah. So what you're saying is you want an API which multiple thread-pools can communicate via to establish a suggested minimum value for the maximum thread count? I'm not opposed to such a thing, but shouldn't this be a deployment / tuning option particular to a configuration? The suggested value would have to be a fairly subtle hint... Maybe something like 'IReactorThreads.suggestAdditionalThreads(suggestingObject, addtlThreadCount)'? The reactor could track the suggesting object with a weakref to decrease the total thread count when it goes away. -- _ \ Glyph Lefkowitz |"Along the shore the cloud waves break, / \ \ glyph@divmod.com | The twin suns sink behind the lake, ` _o_ \-----------------+ The shadows lengthen, In Carcosa" ( ._\ \ - Cassilda's Song, "The King in Yellow", Act 1, Scene 2