On 24 Jul 2007, at 10:35 am, Graham Dumpleton wrote:
Memory use of running multiple Django instances under Apache using mod_python is only one of the problems that can arise in this instance. Other problems are the ability for the Django instances to interfere with each other due to C extension modules which haven't been written properly to be used from multiple sub interpreters at the same time, or even attempts to use different versions of a C extension module from the different Django instances. Using mod_wsgi or mod_fastcgi may therefore be a better solution given they allow separation of the Django instances.
I'm glad you say this, as this has been happening to me and I wasn't sure what was going on. We have about 38 sites running on mod_python/ apache and on odd occasions we get the wrong site appearing, although a swift restart of apache seems to cure it. Presumably the more sites we get, the worse this problem will get and it may be wise for us to look into using mod_fastcgi in future.
Does anyone have any experience of using fastcgi with 30 odd sites? Thanks, David -- David Reynolds [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
