> -----Ursprüngliche Nachricht-----
> Von: Jim Jagielski 
> > 
> 
> Yeah, but we check to see if we're >1 thread, so in prefork,
> we drop to single connection workers.

Which makes sense to me. Why have more than one connection per worker
on a prefork processes that can only handle one request at a time?
As the current connection pool mechanism is limited to share connections
within the same process and not over all processes it is quite clear
that prefork suffers a lot from this approach and the real benefit only
shows up with a threaded MPM that has not "too much" processes. Whatever
"too much" means.

Regards

Rüdiger

Reply via email to