Hello, I've noticed that with recent version of uWSGI, the spooler does not treat jobs as it used to. Before, if 10 jobs were in the queue and job 1 failed, the spooler would proceed to try job 2 and then job 3, etc. But recently, I've noticed that if job1 fails, it will continue to try and execute job1 completely ignoring jobs 2-10 until job1 is successfully processed. Here is my config:
uwsgi: auto-procname: true chdir: /opt/webapps/example.com cpu-affinity: 1 enable-threads: true env: DJANGO_SETTINGS_MODULE=example.settings harakiri: 7200 master: true max-requests: 500 memory-report: true module: django.core.handlers.wsgi:WSGIHandler() pidfile: /opt/webapps/example.com/pid/uwsgi.pid processes: 16 pythonpath: example socket: /opt/webapps/example.com/sock/uwsgi.sock spooler: /opt/webapps/example.com/spooler spooler-chdir: /opt/webapps/example.com spooler-import: custom.uwsgi_utils spooler-max-tasks: 20 vacuum: true virtualenv: /opt/webapps/example.com Also, on a slightly related note.. I've noticed that the spooler workers will occasionally take up VAST amounts of memory (upwards of 256MB) with no jobs in the queue. This is why I've set the spooler-max-tasks option, but it's even happened to me once with that option set. I don't currently have debug logs from when this has happened but I'll post them when it happens to me again. BTW, uWSGI is still the most amazing piece of software EVER. Thank you for all the hard work :) Thanks, Ryan- _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
