[Twisted-Python] Re: twisted application server

Don Dwiggins ddwiggins at advpubtech.com
Thu Mar 6 12:35:38 EST 2008

glyph at divmod.com wrote:
> The other reason is that adbapi is old.  If we were going to implement 
> something like ADBAPI today, we'd probably write a process pool first, 
> but adbapi was written as a quick hack to get some database integration 
> a long time ago.
> The only caveat is that additional Python interpreters take up more RAM 
> than additional threads.  If the database processes are doing any heavy 
> CPU lifting though, this cost could well be worth it.

I'm just getting started with an XMLRPC server that uses adbapi.  This 
satisfies my curiosity as to why it was threaded.  Now assuming that, 
for my application, the "heavy lifting" is done by the DB engine itself, 
is there any good reason to dig into implementing a process pool?  (I'm 
thinking of the future here, as the server begins to grow more 
functionality.  Right now, my main concern is not to block multiple 
simultaneous requests from clients.)

Don Dwiggins
Advanced Publishing Technology

More information about the Twisted-Python mailing list