Graham, the docs state: "For the purposes of this option, being idle means no new requests being received, or no attempts by current requests to read request content or generate response content for the defined period."
This implies to me that a running request that is taking a long time could actually be killed as if it were idle (suppose it were fetching a very slow database query). Is this the case? Also, I'm looking for an ultra-conservative and graceful method of recycling memory. I've read your article on url partitioning, which was useful, but sooner or later, one must rely on either inactivity-timeout or maximum-requests, is that accurate? But both these will eventually, after graceful timeout/shutdown timeout, potentially kill active requests. It is valid for our app to handle long-running reports, so I was hoping for an ultra-safe mechanism. Do you have any advice here? -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
