On Apr 20, 1:08 pm, Greg <gregplaysgui...@gmail.com> wrote:
> Hi all,
>
> My django sites and static media are currently served by the same
> multi-process apache installation, and I'm wondering if it would be
> more efficient — memory-wise — to have a completely seperate apache
> install for media (listening to a seperate IP etc). The media
> installation would have mod_deflate, mod_expires etc installed, and
> the django one would just have mod_wsgi, whereas currently all these
> modules are installed in my one apache config.
>
> I'm not familiar enough with how the Apache / mod_wsgi stack works to
> know whether this would be worthwhile... does anyone know?
>
> Hopefully I'm asking this question in the right place... feel free to
> point me in the right direction if there's a better forum.
How are you currently using mod_wsgi? Are you using embedded mode or
daemon mode? Also, which Apache MPM are you using? Finally, do you
have requirements to run crap like PHP on the same Apache?
There have been various discussions over time about this on the
mod_wsgi list on Google Groups. What is the best setup ultimately
depends on various things, including expected amount of traffic,
whether memory conservation is a priority, whether you have compute
bound tasks being performed by application, or whether it is mostly i/
o bound on disk and database.
Lets at least start with how you have it configured now and can
comment on the merits or otherwise of that configuration and how you
might change things.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
