automatically reload source code as it changes, including inotify(7) support on Linux. Read more... . • Autoscaling Dynamically resizing the worker pool depending on load, or custom metrics specified by the user • Remote control • Commands • Time Limits • Rate Limits • Max tasks per child setting • Autoscaling 92 Chapter 2. Contents Celery Documentation, Release 3.1.25 • Queues • Autoreloading • Inspecting using the workers –maxtasksperchild argument or using the CELERYD_MAX_TASKS_PER_CHILD setting. Autoscaling New in version 2.2. pool support: prefork, gevent The autoscaler component is used to dynamically

automatically reload source code as it changes, including inotify(7) support on Linux. Read more…. Autoscaling Dynamically resizing the worker pool depending on load, or custom metrics specified by the user paths Concurrency Remote control Commands Time Limits Rate Limits Max tasks per child setting Autoscaling Queues Autoreloading Inspecting workers Additional Commands Writing your own remote control commands using the workers –maxtasksperchild argument or using the CELERYD_MAX_TASKS_PER_CHILD setting. Autoscaling New in version 2.2. pool support: prefork, gevent The autoscaler component is used to dynamically

• Time Limits • Rate Limits • Max tasks per child setting • Max memory per child setting • Autoscaling • Queues • Inspecting workers • Additional Commands • Writing your own remote control commands the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support prefork, gevent The autoscaler component is used to dynamically needs two numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: --autoscale=10,3 (always keep 3 processes

control Commands Time Limits Rate Limits Max tasks per child setting Max memory per child setting Autoscaling Queues Inspecting workers Additional Commands Writing your own remote control commands Starting the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support: prefork, gevent The autoscaler component is used to dynamically numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: --autoscale=10,3 (always keep

control Commands Time Limits Rate Limits Max tasks per child setting Max memory per child setting Autoscaling Queues Inspecting workers Additional Commands Writing your own remote control commands Starting the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support: prefork, gevent The autoscaler component is used to dynamically numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: --autoscale=10,3 (always keep

• Time Limits • Rate Limits • Max tasks per child setting • Max memory per child setting • Autoscaling • Queues • Inspecting workers • Additional Commands • Writing your own remote control commands the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support prefork, gevent The autoscaler component is used to dynamically needs two numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: 2.3. User Guide 99 Celery Documentation

• Time Limits • Rate Limits • Max tasks per child setting • Max memory per child setting • Autoscaling • Queues • Inspecting workers • Additional Commands • Writing your own remote control commands the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support prefork, gevent The autoscaler component is used to dynamically needs two numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: --autoscale=10,3 (always keep 3 processes

control Commands Time Limits Rate Limits Max tasks per child setting Max memory per child setting Autoscaling Queues Inspecting workers Additional Commands Writing your own remote control commands Starting the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support: prefork, gevent The autoscaler component is used to dynamically numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: --autoscale=10,3 (always keep

• Time Limits • Rate Limits • Max tasks per child setting • Max memory per child setting • Autoscaling • Queues • Inspecting workers • Additional Commands • Writing your own remote control commands the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support prefork, gevent The autoscaler component is used to dynamically needs two numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: --autoscale=10,3 (always keep 3 processes

• Time Limits • Rate Limits • Max tasks per child setting • Max memory per child setting • Autoscaling • Queues • Inspecting workers • Additional Commands • Writing your own remote control commands the workers --max-memory-per-child argument or using the worker_max_memory_per_child setting. Autoscaling New in version 2.2. pool support prefork, gevent The autoscaler component is used to dynamically needs two numbers: the maximum and minimum number of pool processes: --autoscale=AUTOSCALE Enable autoscaling by providing max_concurrency,min_concurrency. Example: --autoscale=10,3 (always keep 3 processes