I thought I needed multiple Apache's since I frequently have several concurrent requests. The actual dynamic python processing is quick, but since clients could be connected for relatively long (slow connections, etc), I thought I'd need multiple Apache's talking to each. Since Django says it's not officially thread safe, I'm using the prefork MPM in Apache.
I looked at mod_wsgi and decided to try fastcgi since the Django docs explicitly support it. But, given my problems perhaps I'll try mod_wsgi next. On Dec 5, 8:26 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Dec 6, 12:04 pm, TP <[EMAIL PROTECTED]> wrote: > > > I've been using Django for the past few months and had great results > > with Apache and mod_python. However, I'd like to try and reduce the > > amount of memory that is used by having multiple Apache's each with > > their own copy of my application. I decided to try mod_fastcgi in > > Apache and Django's FastCGI server capability. > > Why have multiple Apache's if using mod_fastcgi. You should be able to > hang multiple FASTCGI hosted applications hanging off the one Apache. > > BTW, you might also want to look at mod_wsgi. Allows you to run Django > in separate process of their own just like FASTCGI, but everything > still managed by Apache without the need for you to separately start > Django or use any supervisor system to keep it running. > > 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
