[Twisted-Python] module interface checking tool

Dave Peticolas dave at krondo.com
Tue Aug 10 08:48:14 MDT 2004

On Tue, 2004-08-10 at 06:32, Glyph Lefkowitz wrote:
> On Tue, 2004-08-10 at 01:16, Dave Peticolas wrote:
> > On further thought, I'm not so sure about this. I have a real
> > application that is managing multiple connection pools. If
> > every connection pool is sharing the same threadpool, how
> > can I prevent one connection pool from starving the others,
> > as well as non-adbapi tasks?
> You can easily limit how many outstanding operations can be pending from
> any given pool.  Like I said in a previous email, virtual task !=
> physical thread.  I'll write some example code later today.

I'm not worried about limiting a connection pool to it's
max threads, which is still necessary to do, of course,
and I would be curious to see how your implementation
differs from my own ideas.

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.


More information about the Twisted-Python mailing list