Which apache worker to use with passenger and how?

Question

I've this config in my apache2.conf

<IfModule mpm_prefork_module>
StartServers          5
MinSpareServers       5
MaxSpareServers      10
MaxClients          150
MaxRequestsPerChild   0
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves

<IfModule mpm_worker_module>
StartServers          2
MaxClients          15
MinSpareThreads      4
MaxSpareThreads      5
ThreadsPerChild      15
MaxRequestsPerChild   50000
</IfModule>

Now I'm confused here.

• Which module gets loaded on which conditions?
• The phusion guys have suggested to use the worker module. Since both are present in apache conf file, do I have to comment the mpm_prefork_module or leave it as it is?

Following is my passenger conf file for apache:

LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-2.2.4/ext/apache2/mod_passenger.so
PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.4
PassengerRuby /usr/bin/ruby1.8
PassengerMaxPoolSize 3
PassengerPoolIdleTime 999999
RailsFrameworkSpawnerIdleTime 0
RailsAppSpawnerIdleTime 0

• I'm running just a single Rails 2.3.2 app on 256MB slice at slicehost. I'm not quite satisfied with the performance yet. Are the settings above are any good??

Answer 1

Generally, people ask when their VPS starts hitting swap, is that your situation? This thread is pretty helpful re, using "free" and "top" and switching to MPM worker

http://forum.slicehost.com/comments.php?DiscussionID=3313

These are informative about the settings that don't get talked about much

http://wiki.ninjafocus.net/Ruby_on_Rails

http://programming-gone-awry.blogspot.com/2009/06/how-to-save-much-ram-when-running-rails.html

Answer 2

a. run httpd/apache/httpd2/apache2 -l to see which mpm is loaded (usually is prefork though)
b. to get the worker module you have to install it, I've never done it before though, but I know its an either or proposition, they cannot co-exist
c. If you are anticipating any kind of traffic make sure to set MaxClients (in prefork configuration) to about 20 (starting out) or else your app/passenger will crap out in periods of high traffic
d. For passenger settings, I'd start with

PassengerMaxPoolSize 2
PassengerPoolIdleTime 0
RailsFrameworkSpawnerIdleTime 0
RailsAppSpawnerIdleTime 0

What this does is keep the Framework spawner, App spawner and App instances in memory for the longest possible time, so it does not have to respawn an app instance or the framework after a period of inactivity (if your site is not high traffic). This is as close to running an always-on mongrel-type setup as you'll get.

Answer 3

Whether Apache uses the prefork MPM or the worker MPM is a compile time option. There's no way to change it at runtime so you can't load an MPM.

The directive means "if the current MPM is xxx, then use the configuration inside this block, otherwise ignore this block completely".

So if you want to use the worker MPM then you must uninstall the prefork version and install the worker version.