Celery 2.2 Documentation
RabbitMQ on OS X First steps with Celery Creating a simple task Configuration Running the celery worker server Executing the task Where to go from here Resources Getting Help Bug tracker Wiki Contributing scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet [http://eventlet.net/] or gevent [http://gevent.org/]. Tasks can github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on0 码力 | 505 页 | 878.66 KB | 1 年前3Celery 2.3 Documentation
scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet or gevent. Tasks can execute asynchronously (in the background) Overview This is a high level overview of the architecture. The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on or select different message topologies, by configuration or even at runtime. Remote- control Worker nodes can be controlled from remote by using broadcast messaging. A range of built-in commands exist0 码力 | 334 页 | 1.25 MB | 1 年前3Celery 2.2 Documentation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 10.25 celery.apps.worker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 10.26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 11.2 Internals: The worker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 11.3 Task scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet or gevent. Tasks can execute asynchronously (in the background)0 码力 | 314 页 | 1.26 MB | 1 年前3Celery 2.4 Documentation
First steps with Celery Choosing your Broker Creating a simple task Configuration Running the celery worker server Executing the task Where to go from here Resources Getting Help Bug tracker Wiki Contributing scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet [http://eventlet.net/] or gevent [http://gevent.org/]. Tasks can github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on0 码力 | 543 页 | 957.42 KB | 1 年前3Celery 2.5 Documentation
scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet or gevent. Tasks can execute asynchronously (in the background) Overview This is a high level overview of the architecture. The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on or select different message topologies, by configuration or even at runtime. Remote- control Worker nodes can be controlled from remote by using broadcast messaging. A range of built-in commands exist0 码力 | 400 页 | 1.40 MB | 1 年前3Celery 2.3 Documentation
RabbitMQ on OS X First steps with Celery Creating a simple task Configuration Running the celery worker server Executing the task Where to go from here Resources Getting Help Bug tracker Wiki Contributing scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet [http://eventlet.net/] or gevent [http://gevent.org/]. Tasks can github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on0 码力 | 530 页 | 900.64 KB | 1 年前3Celery 2.4 Documentation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 10.27 celery.apps.worker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 10.28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 11.2 Internals: The worker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 11.3 Task scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet or gevent. Tasks can execute asynchronously (in the background)0 码力 | 395 页 | 1.54 MB | 1 年前3Celery 2.5 Documentation
First steps with Celery Choosing your Broker Creating a simple task Configuration Running the celery worker server Executing the task Where to go from here Resources Getting Help Bug tracker Wiki Contributing scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet [http://eventlet.net/] or gevent [http://gevent.org/]. Tasks can github.com/downloads/celery/celery/Celery-Overview-v4.jpg The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on0 码力 | 647 页 | 1011.88 KB | 1 年前3Celery 3.1 Documentation
Overview First Steps with Celery Choosing a Broker Installing Celery Application Running the celery worker server Calling the task Keeping Results Configuration Where to go from here Troubleshooting Next work across threads or machines. A task queue’s input is a unit of work called a task. Dedicated worker processes constantly monitor task queues for new work to perform. Celery communicates via messages workers. To initiate a task, a client adds a message to the queue, which the broker then delivers to a worker. A Celery system can consist of multiple workers and brokers, giving way to high availability and0 码力 | 887 页 | 1.22 MB | 1 年前3Celery 3.1 Documentation
work across threads or machines. A task queue’s input is a unit of work called a task. Dedicated worker processes constantly monitor task queues for new work to perform. Celery communicates via messages workers. To initiate a task, a client adds a message to the queue, which the broker then delivers to a worker. A Celery system can consist of multiple workers and brokers, giving way to high availability and second/minute/hour, or how long a task can be allowed to run, and this can be set as a default, for a specific worker or individually for each task type. Read more... . • Scheduling You can specify the time to run0 码力 | 607 页 | 2.27 MB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100