On Wednesday, May 13, 2015 at 5:06:47 AM UTC-4, termopro wrote: > > > No. >> >> Cheers >> >> Tom >> > > OK > <https://www.google.com/search?q=Apache+performance+problems&ie=utf-8&oe=utf-8#q=apache+eating+memory> > > :) >
That's only evidence that a lot of people don't know how to "performance-tune" (a.k.a. configure) Apache. The question you asked Tom was "Doesn't Apache create new process for each request [thus eating memory when serving large amounts of static files during traffic peaks]?", and the reason that Tom correctly answers "No" is that as far as "serving large amounts of static files" goes you should be using mpm-worker (multi-threaded Apache) which most definitely does not spawn a new process for each request. The reason for those search results is that mpm-prefork does, however, spawn a process per request, but it is only needed for non-thread-safe environments (most notoriously mod_php) and you shouldn't have to use it as long as you've been a good coder and avoided global state in your Django app (e.g. keep request-specific shared-state thread-local). I think the reason a lot of people seem to run mpm-prefork is just that it's the default multi-processing module for Apache on most (all?) *nix platforms and they don't know any better. Hope that helps explain away that myth! :) Best wishes, Jonathan -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/425d7d29-e6e3-495f-9901-239570a96622%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
