Why prefork and not worker MPM for Apache

All the Sun-related docs that I can find say to compile Apache using the prefork MPM. Even the CSQAmp Apache is compiled with the prefork MPM. My personal experience is that the worker MPM is much more efficient for Apache 2.0. This site agrees: http://www.stdlib.net/~colmmacc/2006/03/23/niagara-vs-ftpheanetie-showdown/

I'm going to test both myself, but does anyone have any ideas why Sun prefers the prefork MPM?

[430 byte] By [justinellisona] at [2007-11-26 16:09:34]

«« Help!! Counting Lines in a text file.
»» reading 'changes' from retroChangeLog in 5.2

# 1

We chose to build with pre-fork MPM based on the many customer deployments we have seen. Many of our customers use custom modules or php extensions that are not thread-safe. Further, we've seen problems with SSL under heavy load.

Feel free to build in worker mode - it will run and perform well on Solaris.

Shanti

shantiSa at 2007-7-8 22:31:53 >

top of Java-index,Open Source Technologies,OpenSPARC...

# 2

Don't forget the event mpm.Giving people a choice of mpm by having multiple Apache packages would imho be the best choice.

mads_toftuma at 2007-7-8 22:31:53 >

OpenSPARC

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

Why prefork and not worker MPM for Apache

Open Source Technologies New Topic

Open Source Technologies Hot Topic

Open Source Technologies

All Classified