Celery 3.1 DocumentationLinux. Read more…. Autoscaling Dynamically resizing the worker pool depending on load, or custom metrics specified by the user, used to limit memory usage in shared hosting/cloud environments or to enforce You can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with0 码力 | 887 页 | 1.22 MB | 1 年前3
Celery 3.1 DocumentationRead more... . • Autoscaling Dynamically resizing the worker pool depending on load, or custom metrics specified by the user, used to limit memory usage in shared hosting/cloud environments or to enforce0 码力 | 607 页 | 2.27 MB | 1 年前3
Celery v4.0.1 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with0 码力 | 1040 页 | 1.37 MB | 1 年前3
Celery v4.0.2 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery v4.1.0 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with0 码力 | 1057 页 | 1.35 MB | 1 年前3
Celery 4.0 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with0 码力 | 1042 页 | 1.37 MB | 1 年前3
Celery v5.0.1 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with start, # but this will only work the first time we start, as # maxtasksperchild will mess up metrics. if not obj.restart_count and not obj.pool.did_start_ok(): raise WorkerLostError('Could0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery 3.0 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with start, # but this will only work the first time we start, as # maxtasksperchild will mess up metrics. if not obj.restart_count and not obj.pool.did_start_ok(): raise WorkerLostError('Could0 码力 | 2110 页 | 2.23 MB | 1 年前3
Celery v4.0.0 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with start, # but this will only work the first time we start, as # maxtasksperchild will mess up metrics. if not obj.restart_count and not obj.pool.did_start_ok(): raise WorkerLostError('Could0 码力 | 2106 页 | 2.23 MB | 1 年前3
Celery v5.0.2 DocumentationYou can also define your own rules for the autoscaler by subclassing Autoscaler. Some ideas for metrics include load average or the amount of memory available. You can specify a custom autoscaler with start, # but this will only work the first time we start, as # maxtasksperchild will mess up metrics. if not obj.restart_count and not obj.pool.did_start_ok(): raise WorkerLostError('Could0 码力 | 2313 页 | 2.14 MB | 1 年前3
共 24 条
- 1
- 2
- 3













