Switch service callback workers to use eventlet pool implementation

Service callbacks are I/O bound and can take a long time if the
callback URL takes a long time to respond. This is a perfect use
case for an eventlet worker pool since it allows spawning multiple
green threads (1000 in the proposed configuration) to execute HTTP
requests concurrently without a significant increase in CPU load
or memory usage needed for adding additional worker processes.
This commit is contained in:
Alexey Bezhan
2018-02-12 16:19:23 +00:00
parent 9eada23392
commit 2dfbd93c7e

View File

@@ -95,6 +95,6 @@ applications:
NOTIFY_APP_NAME: delivery-worker-receipts
- name: notify-delivery-worker-service-callbacks
command: scripts/run_app_paas.sh celery -A run_celery.notify_celery worker --loglevel=INFO --concurrency=11 -Q service-callbacks
command: scripts/run_app_paas.sh celery -A run_celery.notify_celery worker --loglevel=INFO -P eventlet -c 1000 -Q service-callbacks
env:
NOTIFY_APP_NAME: delivery-worker-service-callbacks
NOTIFY_APP_NAME: delivery-worker-service-callbacks