Tyrant backend settings Redis backend settings MongoDB backend settings Messaging settings Task execution settings Worker: celeryd Periodic Task Server: celerybeat Monitor Server: celerymon Cookbook Creating distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on a single or more worker servers. Tasks can execute class. This is a handy shortcut to the apply_async method which gives greater control of the task execution. See Executing Tasks for more information. >>> from tasks import add >>> add.delay(4, 4)

0 码力 | 221 页 | 283.64 KB | 1 年前

3

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on a single or more worker servers. Tasks can execute class. This is a handy shortcut to the apply_async method which gives greater control of the task execution. See Execut- ing Tasks for more information. >>> from tasks import add >>> add.delay(4, 4) execution. See Executing Tasks for more information. >>> from myapp.tasks import MyTask >>> MyTask.delay(some_arg="foo")

Tyrant backend settings Redis backend settings MongoDB backend settings Messaging settings Task execution settings Worker: celeryd Periodic Task Server: celerybeat Monitor Server: celerymon Cookbook Creating distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on a single or more worker servers. Tasks can execute This is a handy shortcut to the apply_async() method which gives greater control of the task execution. Read the Executing Tasks part of the user guide for more information about executing tasks. >>>

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on a single or more worker servers. Tasks can execute This is a handy shortcut to the apply_async() method which gives greater control of the task execution. Read the Executing Tasks part of the user guide for more information about executing tasks. >>> State – Database transactions 2.1.1 Basics A task is a class that encapsulates a function and its execution options. Given a function create_user, that takes two arguments: username and password, you can

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes. Tasks can execute asynchronously This is a handy shortcut to the apply_async() method which gives greater control of the task execution (see Executing Tasks). >>> from tasks import add >>> add.delay(4, 4) model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes. Tasks can execute asyn- This is a handy shortcut to the apply_async() method which gives greater control of the task execution (see Executing Tasks). >>> from tasks import add >>> add.delay(4, 4) model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing limits can be set for each task type, or globally for all. Routing Using AMQP’s flexible routing model you can route tasks to different workers, or select different message topologies, by configuration This is a handy shortcut to the apply_async() method which gives greater control of the task execution (see Executing Tasks). >>> from tasks import add >>> add.delay(4, 4)

0 码力 | 334 页 | 1.25 MB | 1 年前

3

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing limits can be set for each task type, or globally for all. Routing Using AMQP’s flexible routing model you can route tasks to different workers, or select different message topologies, by configuration This is a handy shortcut to the apply_async() method which gives greater control of the task execution (see Executing Tasks). >>> from tasks import add >>> add.delay(4, 4)

0 码力 | 505 页 | 878.66 KB | 1 年前

3

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing limits can be set for each task type, or globally for all. Routing Using AMQP’s flexible routing model you can route tasks to different workers, or select different message topologies, by configuration This is a handy shortcut to the apply_async() method which gives greater control of the task execution (see Executing Tasks). >>> from tasks import add >>> add.delay(4, 4)

0 码力 | 314 页 | 1.26 MB | 1 年前

3

distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing limits can be set for each task type, or globally for all. Routing Using AMQP’s flexible routing model you can route tasks to different workers, or select different message topologies, by configuration This is a handy shortcut to the apply_async() method which gives greater control of the task execution (see Executing Tasks). >>> from tasks import add >>> add.delay(4, 4)

0 码力 | 530 页 | 900.64 KB | 1 年前

3