For gunicorn I have 2 workers:
gunicorn:
[program:xxx]
command=/usr/local/bin/gunicorn_django -w 2 -b 127.0.0.1:8002 --timeout
600 /usr/local/src/pythonapps/xxx/app/settings_production.py
directory=/usr/local/src/pythonapps/xxx
user=www-data
autostart=true
autorestart=true
stdout_logfile=/var/log/supervisor/xxx.supervisord.log
redirect_stderr=true
Now I try app to apache and benchmark it.
On Mon, 19 Dec 2011 13:15:09 +0100, kenneth gonsalves
<law...@thenilgiris.com> wrote:
On Mon, 2011-12-19 at 02:17 -0800, pixelfields wrote:
but ... this not solved my problem. I increase worker_processes to 2,
but during test I still have processor overload 98% - 100%.
how many workers do you have for gunicorn? Also do you have the same
problem when using some other webserver with nginx (or apache with
mod_wsgi)?
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
