Celery 2.0 Documentation- celery.messaging Contrib: Abortable tasks - celery.contrib.abortable Events - celery.events In-memory Representation of Cluster State - celery.events.state Celery Worker Daemon - celery.bin.celeryd Celery application. blog/models.py The comment model looks like this: from django.db import models from django.utils.translation import ugettext_lazy as _ class Comment(models.Model): name = models.CharField(_("name") tasks from blog.models import Comment class CommentForm(forms.ModelForm): class Meta: model = Comment def add_comment(request, slug, template_name="comments/create.html"): post = get_object_or_404(Entry0 码力 | 284 页 | 332.71 KB | 1 年前3
 Celery 2.0 Documentationapplication. blog/models.py The comment model looks like this: from django.db import models from django.utils.translation import ugettext_lazy as _ class Comment(models.Model): name = models.CharField(_("name") blog import tasks from blog.models import Comment class CommentForm(forms.ModelForm): class Meta: model = Comment def add_comment(request, slug, template_name="comments/create.html"): post = get_object_or_404(Entry processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst being a full transfer from another continent. If the data is far away, you could try0 码力 | 165 页 | 492.43 KB | 1 年前3
 Celery 2.2 Documentationlimits 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 Figure 2: Worker bindings. Go to Routing Tasks. Celery takes advantage of AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst would be a full transfer from another continent. If the data is far away, you could try0 码力 | 314 页 | 1.26 MB | 1 年前3
 Celery 2.2 Documentationlimits 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 Figure 2: Worker bindings. Go to Routing Tasks. Celery takes advantage of AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst would be a full transfer from another continent. If the data is far away, you could try0 码力 | 505 页 | 878.66 KB | 1 年前3
 Celery 2.3 Documentationlimits 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 Figure 2: Worker bindings. Go to Routing Tasks. Celery takes advantage of AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst would be a full transfer from another continent. If the data is far away, you could try0 码力 | 334 页 | 1.25 MB | 1 年前3
 Celery 2.5 Documentationlimits 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 Figure 2: Worker bindings. Go to Routing Tasks. Celery takes advantage of AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst would be a full transfer from another continent. If the data is far away, you could try0 码力 | 400 页 | 1.40 MB | 1 年前3
 Celery 1.0 Documentationapplication. blog/models.py The comment model looks like this: from django.db import models from django.utils.translation import ugettext_lazy as _ class Comment(models.Model): name = models.CharField(_("name") tasks from blog.models import Comment class CommentForm(forms.ModelForm): class Meta: model = Comment def add_comment(request, slug, template_name="comments/create.html"): post = get_object_or_404(Entry processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst being a full transfer from another continent. If the data is far away, you could try0 码力 | 221 页 | 283.64 KB | 1 年前3
 Celery 2.1 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 9.22 In-memory Representation of Cluster State - celery.events.state . . . . . . . . . . . . . . . . . . . . 156 Figure 2: Worker bindings. Go to Routing Tasks. Celery takes advantage of AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst would be a full transfer from another continent. If the data is far away, you could try0 码力 | 285 页 | 1.19 MB | 1 年前3
 Celery 1.0 Documentation(stable) blog/models.py The comment model looks like this: from django.db import models from django.utils.translation import ugettext_lazy as _ class Comment(models.Model): name = models.CharField(_("name") blog import tasks from blog.models import Comment class CommentForm(forms.ModelForm): class Meta: model = Comment def add_comment(request, slug, template_name="comments/create.html"): post = get_object_or_404(Entry processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst being a full transfer from another continent. If the data is far away, you could try0 码力 | 123 页 | 400.69 KB | 1 年前3
 Celery 2.1 Documentation- celery.messaging Contrib: Abortable tasks - celery.contrib.abortable Events - celery.events In-memory Representation of Cluster State - celery.events.state App: Worker Node - celery.apps.worker App: Figure 2: Worker bindings. Go to Routing Tasks. Celery takes advantage of AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different processing the task should be as close to the data as possible. The best would be to have a copy in memory, the worst would be a full transfer from another continent. If the data is far away, you could try0 码力 | 463 页 | 861.69 KB | 1 年前3
共 51 条
- 1
 - 2
 - 3
 - 4
 - 5
 - 6
 













