I just created a new django app (python 2.7, django 1.3.1) and I noticed some changes in httpd.conf. It looks like the number of processes were reduced, and more threads were added. I also noticed these new config items:
Just curious how, overall, these new changes will impact my django apps, and why they were implemented.
--------- edit ----------- asked 14 Sep '11, 17:47 Cole |
We added those parameters as the result from a recommendation from the mod_wsgi developer. The net effect is that an idle app will use around 10-15MB less memory than it did without those parameters. answered 14 Sep '11, 17:52 seanf I just had to comment out the three lines above in order to get my project running. I set-up a staging server and copied over an existing django project into a new django webapp. However, my new staging server wasn't able to import some of the django apps listed in my settings.py. Once I commented out the three lines above, it started working. I don't know if this is relevant but the two django apps that caused problems were both symlinked from the project root.
(14 Sep '11, 21:12)
Cole
Likely, you will want to check your apache config and sys.path that Django is getting. An easy way to do this is to put this in settings.py
This will send the sys.path that the whole stack is setting to the error log and you can see if any need to be set.
(14 Sep '11, 21:26)
johns
I'll take another look at this soon, when my current deadline is met. Thanks!
(14 Sep '11, 22:18)
Cole
|