Graham, thanks for you feedback. Very interesting to understand better what's going on. Indeed, it sounds like this could happen in my current configuration too, though in practice supervisor kills one by one very slow processes without minding what's really going on. Less drastic that my previous solution (monit, who would restart the whole apache!) yet not fully optimal.
I agree that I'd rather users see 503 when too many requests start piping up rather than having a long backlog building up. In addition, as you mention, many users might simply abandon when loading gets too load, and just retry a bit later. It should definitely work better as an average overall experience. I'll definitely keep following the mailing list and the google docs wiki (PS., and I do know how difficult and tedious and long that is, but by any mean keep up-to-date the wiki especially when you feel 4.0 is mature!) thanks, Stefano -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To view this discussion on the web visit https://groups.google.com/d/msg/modwsgi/-/qA73RUPFWHQJ. 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.
