Since I was looking for some more in-depth answers, I decided to research the issue myself in depth. Please let me know if I’ve misunderstood anything.
Some general recommendation are to use a separate webserver for handling media. By separate, I mean a webserver which is not running Django. This server can be for instance:
- Lighttpd (Lighty)
- Nginx (EngineX)
- Or some other light-weight server
Then, for Django, you can go down different paths. You can either:
-
Serve Django via Apache and:
-
mod_python
This is the stable and recommended/well documented way. Cons: uses a lot of memory.
-
mod_wsgi
From what I understand, mod_wsgi is a newer alternative. It appears to be faster and easier on resources.
-
mod_fastcgi
When using FastCGI you are delegating the serving of Django to another process. Since mod_python includes a python interpreter in every request it uses a lot of memory. This is a way to bypass that problem. Also there is some security concerns.
What you do is that you start your Django FastCGI server in a separate process and then configures apache via rewrites to call this process when needed.
-
Or you can:
-
Serve Django without using Apache but with another server that supports FastCGI natively:
(The documentation mentions that you can do this if you don’t have any Apache specific needs. I guess the reason must be to save memory.)
- Lighttpd
This is the server that runs Youtube. It seems fast and easy to use, however i’ve seen reports on memoryleaks.
- nginx
I’ve seen benchmarks claiming that this server is even faster than lighttpd. It’s mostly documented in Russian though.
Another thing, due to limitations in Python your server should be running in forked mode, not threaded.
So this is my current research, but I want more opinions and experiences.