mozilla
/
treeherder
зеркало из https://github.com/mozilla/treeherder.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
treeherder/Procfile

16 строки
2.1 KiB
Plaintext
Исходник Обычный вид История

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
2017-08-04 18:49:17 +03:00
web: newrelic-admin run-program gunicorn treeherder.config.wsgi:application --timeout 20
Bug 1215102 - Adjust Celery settings to match CloudAMQP recommendations CloudAMQP recommend disabling events/heartbeats/gossip/mingle messages, in order to reduce unnecessary load on the rabbitmq server: https://www.cloudamqp.com/docs/celery.html For settings reference, see: http://docs.celeryproject.org/en/3.1/configuration.html http://docs.celeryproject.org/en/3.1/whatsnew-3.1.html#gossip-worker-worker-communication http://docs.celeryproject.org/en/3.1/reference/celery.bin.worker.html#cmdoption-celery-worker--without-gossip The Procfile is now becoming exceptionally verbose, however that's a problem to consider solving in another bug, perhaps via a runner script.
2017-02-14 02:01:13 +03:00
worker_beat: newrelic-admin run-program celery beat -A treeherder
Bug 1340132 - Reduce usage of --maxtasksperchild with celery Now we're no longer using datasource, the memory leaks previously seen have gone. As such there is no need to make the celery worker processes restart so frequently (they will now only be restarted at the daily Heroku dyno restart), which will improve performance. In addition, this will reduce the number of transactions that don't get reported to New Relic (when the maxtasksperchild threshold is reached, the worker is forcibly killed before it can submit the New Relic payload). The log parser tasks have been left unchanged for now, since they appear to still be leaking.
2017-05-05 00:26:43 +03:00
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
worker_buildapi_running: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q buildapi_running --concurrency=5
worker_buildapi_4hr: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q buildapi_4hr --concurrency=1
worker_store_pulse_jobs: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q store_pulse_jobs --concurrency=3
worker_store_pulse_resultsets: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q store_pulse_resultsets --concurrency=3
Bug 1266229 - Allocate Heroku dynos for pulse queue reading
2016-06-02 02:51:26 +03:00
worker_read_pulse_jobs: newrelic-admin run-program ./manage.py read_pulse_jobs
Bug 1336272 - Refactor changing wording from resultset to push (#2644) Change of new environment variable `PULSE_PUSH_SOURCES`. Keep old `publish-resultset-runnable-job-action` task name by creating a method that points to `publish_push_runnable_job_action`.
2017-08-04 19:38:57 +03:00
worker_read_pulse_pushes: newrelic-admin run-program ./manage.py read_pulse_pushes
Bug 1419965 - Remove the estimated job time remaining backend (#2990) The UI has already been removed. This cleans up the data ingestion and removes the `JobDuration` model, however leaves the `running_eta` field on the `Job` model for the next time that table is touched (since the table is large, so altering the schema would likely require downtime).
2017-12-05 01:09:38 +03:00
worker_default: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q default,cycle_data,fetch_bugs,fetch_runnablejobs,generate_perf_alerts,seta_analyze_failures --concurrency=3
Bug 1340132 - Reduce usage of --maxtasksperchild with celery Now we're no longer using datasource, the memory leaks previously seen have gone. As such there is no need to make the celery worker processes restart so frequently (they will now only be restarted at the daily Heroku dyno restart), which will improve performance. In addition, this will reduce the number of transactions that don't get reported to New Relic (when the maxtasksperchild threshold is reached, the worker is forcibly killed before it can submit the New Relic payload). The log parser tasks have been left unchanged for now, since they appear to still be leaking.
2017-05-05 00:26:43 +03:00
worker_hp: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q classification_mirroring,publish_to_pulse --concurrency=1
Bug 1215102 - Adjust Celery settings to match CloudAMQP recommendations CloudAMQP recommend disabling events/heartbeats/gossip/mingle messages, in order to reduce unnecessary load on the rabbitmq server: https://www.cloudamqp.com/docs/celery.html For settings reference, see: http://docs.celeryproject.org/en/3.1/configuration.html http://docs.celeryproject.org/en/3.1/whatsnew-3.1.html#gossip-worker-worker-communication http://docs.celeryproject.org/en/3.1/reference/celery.bin.worker.html#cmdoption-celery-worker--without-gossip The Procfile is now becoming exceptionally verbose, however that's a problem to consider solving in another bug, perhaps via a runner script.
2017-02-14 02:01:13 +03:00
worker_log_parser: newrelic-admin run-program celery worker -A treeherder --without-gossip --without-mingle --without-heartbeat -Q log_parser,log_parser_fail,log_store_failure_lines,log_store_failure_lines_fail,log_crossreference_error_lines,log_crossreference_error_lines_fail,log_autoclassify,log_autoclassify_fail --maxtasksperchild=50 --concurrency=7
Bug 1165229 - Heroku: Move the deploy tasks to their own script Since we'll soon be adding reporting deploys to New Relic, which will be too verbose to include in the Procfile. Also adds additional log output (which follows the buildpack compile log formatting convention) to make it easier to find & follow the release tasks on Papertrail. Uses the `set -euo pipefail` recommendation from: http://redsymbol.net/articles/unofficial-bash-strict-mode/
2016-03-11 14:33:25 +03:00
release: ./bin/pre_deploy