Django Deployment: Cutting Apache's Overhead

Question

I have a small VPS server that has a Nginx front end that serves up static media files and passes Django requests back to an Apache 2.2 prefork MPM server running mod_wsgi.<

Answer 1

For the record, the OP's use of the term MPM is non sensical. The MPM in Apache isn't an option, you are always using an MPM when using Apache. The choice is which MPM you are using. On UNIX the two main MPMs or Multiprocessing Modules, are prefork and worker. On Windows the winnt MPM is always used. Details about the different MPMs can be found in Apache documentation on Apache web site. In the context of mod_wsgi though, you might be better off reading:

http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading

In short though:

• prefork MPM is multi process/single threaded.
• worker MPM is multi process/multi threaded.
• winnt MPM in single process/multi threaded.