[uwsgi]
http=0.0.0.0:8000
module=laalaa.wsgi:application
master=True
pidfile=/tmp/master.pid
vacuum=True
max-requests=5000
env=DJANGO_SETTINGS_MODULE=laalaa.settings
enable-threads=True
processes=2
harakiri=30
post-buffering=1
smart-attach-daemon=/tmp/celery.pid /usr/local/bin/python /home/app/manage.py celery worker -A laalaa --concurrency=10 --loglevel=INFO --pidfile=/tmp/celery.pid

[uwsgi]
http=0.0.0.0:8000
module=laalaa.wsgi:application
master=True
pidfile=/tmp/master.pid
vacuum=True
max-requests=5000
env=DJANGO_SETTINGS_MODULE=laalaa.settings
enable-threads=True
processes=2
harakiri=30
post-buffering=1
smart-attach-daemon=/tmp/celery.pid /usr/local/bin/python /home/app/manage.py celery worker -A laalaa --concurrency=2 --loglevel=INFO --pidfile=/tmp/celery.pid

Reduce celery worker concurrency to 2 threads
Reduce celery worker concurrency to 2 threads

As these workers each make a request to postcodeinfo service, 10 threads
tend to overwhelm the service.

Reducing the concurrency count seems to be a good stopgap solution.

Once we switch providers we can probably switch this back. Or at least
understand if we can do bulk latitude/longitude lookups without so many
requests.
