On 28 Sep 2005, at 21:25, Jacob Kaplan-Moss wrote:
Why? In case you hadn't noticed, Django has a pretty large memory footprint; between Apache, mod_python, Python, the database drivers, etc., Apache server processes tend to weigh about 10M each (at least on my servers). Unfortunately, Apache reuses processes these server processes for a certain number of requests (see the MaxRequestsPerChild directive), but although the server processes grow their memory footprint to accommodate Django, they never shrink.
That's more a limitation of mod_python than of Django itself. I imagine that FastCGI and SCGI avoid this issue almost entirely - the modules themselves are much smaller so it's less wasteful to use them to serve static files as well as Django stuff.
