I think that for a small community one process is enough, I cannot exactly tell when you need a second. You can try estimating from your "requests per second" data and the time to produce a response (100-300ms depending on the page and the hardware). Only considerably popular sites have more than one request per second. This site can live on a single process no problems.
Evgeny ( 2012-04-28 17:11:14 -0500 )editmy processess situation is the same as in this post, (I use django 1.3.1 but I suppose that doesn't change things). So I see 4 processes, the 2 big of which use ~55MB each (the other two, no more than 5MB each). Is it in the httpd.conf file of apache where I configure number of processes, so that I turn it to use only one? thanks again Evgeny, you're really helping us out!
zaf ( 2012-04-28 17:22:50 -0500 )editHere unfortunately I cannot help much - that depends on how webfaction is setting things up. How is python run under apache (it's apache I assume), mod_wsgi? httpd.conf should be the place to look. How much of that file you can edit manually - don't know. I'd ask the webfaction guys.
Evgeny ( 2012-04-28 17:37:37 -0500 )editYeah it's apache. I have my own conf file and I can edit it [already have :) to add authentication until site is live]. Possible lines for update are:
`MaxSpareThreads 3
MinSpareThreads 1
ThreadsPerChild 5
WSGIDaemonProcess myDjangoApp processes=2 threads=12 python-path=/home/myUserName/webapps/myDjangoApp:/home/myUserName/webapps/myDjangoApp/lib/python2.6`
Any idea on what to update to have one process? meanwhile i'll ask webfaction too.
zaf ( 2012-04-28 17:40:55 -0500 )edit