Fix #997: Added support for CELERYD_CONCURRENCY env var to control the number of worker processes
This commit is contained in:
parent
b38a72e129
commit
51b0a571c0
5 changed files with 12 additions and 12 deletions
|
|
@ -86,6 +86,12 @@ REVERSE_PROXY_TYPE=nginx
|
|||
# For the Celery/asynchronous tasks part:
|
||||
# CELERY_BROKER_URL=redis+socket:///run/redis/redis.sock?virtual_host=0
|
||||
|
||||
# Number of worker processes to execute. Defaults to 0, in which case it uses your number of CPUs
|
||||
# Celery workers handle background tasks (such file imports or federation
|
||||
# messaging). The more processes a worker gets, the more tasks
|
||||
# can be processed in parallel. However, more processes also means
|
||||
# a bigger memory footprint.
|
||||
# CELERYD_CONCURRENCY=0
|
||||
|
||||
# Where media files (such as album covers or audio tracks) should be stored
|
||||
# on your system?
|
||||
|
|
@ -175,4 +181,4 @@ AWS_STORAGE_BUCKET_NAME=
|
|||
# If you are using Amazon S3, use this setting to configure how long generated URLs should stay
|
||||
# valid. The default value is 3600 (60 minutes). The maximum accepted value is 604800 (7 days)
|
||||
|
||||
# AWS_QUERYSTRING_EXPIRE=
|
||||
# AWS_QUERYSTRING_EXPIRE=
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue