On 11/08/2010 04:40 PM, Torsten Bronger wrote:
I believe it is because you aren't starting enough servers/keeping
enough spare servers
I don't believe that it could take 200 seconds (did you perhaps read
milliseconds?) to launch another apache process. For me, it seems
that some code waits for a timeout.
- Launch another apache process
- Read in the whole python stack
- init WSGI
- read in all the eggs
- read in all the environment bits
Yeah, 200 seconds seems really long, but there is a lot going on.
I'm not saying I'm right, just that it's an idea which might be worth
investigating.
--
Matthew Caron
Build Engineer
Sixnet | www.sixnet.com
O +1 518 877 5173 Ext. 138
F +1 518 602 9209
[email protected]
--
You received this message because you are subscribed to the Google Groups "Trac
Users" 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/trac-users?hl=en.
