Bug 1387487 - Reduce gunicorn maximum request time to 20 seconds

To ensure that:
* the Heroku router's 30 second timeout doesn't beat gunicorn to it,
  given that routing time is included in Heroku's timing
* the app is more likely to remain responsive, when receiving many
  badly filtered API calls
This commit is contained in:
Ed Morley 2017-08-04 16:49:17 +01:00
Родитель c6e0c26bc8
Коммит 33fa97ec84
2 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -1,4 +1,4 @@
web: newrelic-admin run-program gunicorn treeherder.config.wsgi:application --timeout 29
web: newrelic-admin run-program gunicorn treeherder.config.wsgi:application --timeout 20
worker_beat: newrelic-admin run-program celery beat -A treeherder
worker_pushlog: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q pushlog --concurrency=5
worker_buildapi_pending: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q buildapi_pending --concurrency=5

Просмотреть файл

@ -13,4 +13,4 @@ exec newrelic-admin run-program gunicorn -w $NUM_WORKERS \
treeherder.config.wsgi:application \
--keep-alive=3 \
--log-level error \
--timeout=30
--timeout=20