On 22/09/2012, at 4:54 AM, Kent <[email protected]> wrote: > On Friday, September 7, 2012 1:43:12 AM UTC-4, Graham Dumpleton wrote: > > What this is therefore showing is where the daemon mode processes get > overloaded, although does require Apache worker processes still having > enough threads to keep accepting requests and let them back up in the > worker processes rather than the listener queue, otherwise time stamp > not applied. > > > Should I understand that the prefork MPM will defeat being able to use > mod_wsgi.queue_start value? That is, with prefork MPM, are all the requests > doomed to stay in the listener queue until the daemon process is ready for it > anyway, making the mod_wsgi.queue_start value meaningless?
The queue start time in embedded mode only really shows where a request was delayed due to the initial loading of the WSGI script file. In both embedded and daemon mode, if connections start backing up in the external listener socket, eg port 80, then you don't get visibility of that. The only partial solution for that is using end user monitoring of something like New Relic. Which can show network time between browser client and server. It can't distinguish though whether that was general network time, or time spent waiting for connection to be accepted. Graham -- 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.
