On 7/27/09 3:52 PM, gert wrote: > On Jul 27, 10:06 pm, mixedpuppy<[email protected]> wrote: >> I'm using mod_wsgi for an application that takes several seconds to >> load when a new daemon process is started. The problem is, when the >> processes restart (via maxrequest setting), even with the use of >> WSGIImportScript there is a potential lag in availability. >> WSGIImportScript solves a part of the problem I would like to address, >> but not everything. >> >> The thought occurred to me, why not start a new daemon process at >> (maxrequests - X) requests to give it time to get started and preload >> the application. Better yet, at maxrequests start a new daemon but >> keep handling requests until receiving a signal (or a configured >> timeout) from the new process that it is ready to handle requests. >> >> Curious of this sounds reasonable. > > What happens if you start 2 daemons and kill one manually not using > maxrequest ?
That's a different code path in mod_wsgi so that situation would remain unchanged. There is a specific code path that handles this when max requests is hit. Shane --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
