[Jenkins-infra] Apache on cucumber. prefork vs multi-thread
kk at kohsuke.org
Tue May 27 23:18:49 UTC 2014
What's the downside of changing Apache on jenkins-ci.org from pre-fork
to multi-threaded one?
In looking at mod_status output, I get the impression that apache
processes spend a lot of time in reading, closing, or in keep alive state.
The only way to handle them would be to increase the process pool size,
but prefork means postgres connections would have to grow linearly, even
though most of the time they are idle.
It seems to me that we can serve far greater number of requests
concurrently with smaller number of postgres connections if we use
Is that worth experimenting?
Kohsuke Kawaguchi http://kohsuke.org/
More information about the Jenkins-infra