[Web-SIG] multi-threaded or multi-process wsgi apps

[William Dode]

On 26-11-2007, Chris Withers wrote:
> Hey All,
>
> I hope I have the right list, if not please point me in the right 
> direction...
>
> Likewise, if there are good docs that cover all of this, please send me 
> their way ;-)
>
> Right, I'm curious as to how wsgi applications end up being 
> multi-threaded or multi-process and if they are, how they share 
> resources such as databases and configuration.
>
> There's a couple of reasons I'm asking...
>
> The first was something Chris McDonough said about one ofthe issues 
> they're having with the repoze project: when using something like 
> mod_wsgi, it's the first person to hit each thread that takes the hit of 
> loading the configuration and opening up the zodb. Opening the ZODB, in 
> particular, can take a lot of time. How should repoze be structured such 
> that all the threads load their config and open their databases when 
> apache is restarted rather than when each thread is first hit?

What about using a distributed object system like pyro ? You could have 
the heavy loading of the database in a server independant of the wsgi 
application.

http://pyro.sourceforge.net/

-- 
William Dodé  -  http://flibuste.net
Informaticien indépendant