I'm unsure if this is a simple to answer issue or not. We've been using django simply for a while and are now starting to use it in a more production like setting. Since apache is our preferred server we tried using a single apache server with mod_python in virtual hosts. Each virtual host had its own interpreter, but for various reasons we decided it was too hard to prevent intra-interpreter interactions. The main problem being our own C accelerators; we currently don't have time to rewrite these to allow easy use with multiple interpreters/threads.
Currently I am trying a two level approach with proxying; it seems to work. The apache in the second level handles only one of the upper level virtual hosts and since they are in a different process no interactions can happen. Clearly we have more apache processes than before and the restarts are harder etc etc.
Is there a better way to handle this sort of thing using fastcgi or scgi? Can we get all requests from a particular host to be handled in only one group of processes. Our back end process doesn't respond well to being threaded and it can take a long time to complete so we seem to need a worker pool for each virtual host.
Any ideas welcome. -- Robin Becker --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
