Celery 1.0 Documentationblog/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"), max_length=64) 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 try incre- ment its count by. clickmuncher/models.py: from django.db import models from django.utils.translation import ugettext_lazy as _ class ClickManager(models.Manager): def increment_clicks(self, for_url0 码力 | 123 页 | 400.69 KB | 1 年前3
Celery 1.0 Documentationblog/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"), 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 try increment its count by. clickmuncher/models.py: from django.db import models from django.utils.translation import ugettext_lazy as _ class ClickManager(models.Manager): def increment_clicks(self, for_url0 码力 | 221 页 | 283.64 KB | 1 年前3
Celery 2.0 Documentationblog/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"), max_length=64) 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 try of tasks a worker can execute before it’s replaced by a new process. This is useful if you have memory leaks you have no control over for example from closed source C extensions. The option can be set0 码力 | 165 页 | 492.43 KB | 1 年前3
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 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"), 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 码力 | 284 页 | 332.71 KB | 1 年前3
Celery 2.1 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 9.22 In-memory Representation of Cluster State - celery.events.state . . . . . . . . . . . . . . . . . . . . 156 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 try 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"), max_length=64)0 码力 | 285 页 | 1.19 MB | 1 年前3
Celery 2.2 Documentationprocessing 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 try 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"), max_length=64) sending a broadcast message to all the workers, the workers then keep a list of revoked tasks in memory. If you want tasks to remain revoked after worker restart you need to specify a file for these to0 码力 | 314 页 | 1.26 MB | 1 年前3
Celery 2.3 Documentationprocessing 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 try 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"), max_length=64) sending a broadcast message to all the workers, the workers then keep a list of revoked tasks in memory. If you want tasks to remain revoked after worker restart you need to specify a file for these to0 码力 | 334 页 | 1.25 MB | 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: 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 try 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"),0 码力 | 463 页 | 861.69 KB | 1 年前3
Celery 2.2 Documentationprocessing 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 try 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"), sending a broadcast message to all the workers, the workers then keep a list of revoked tasks in memory. If you want tasks to remain revoked after worker restart you need to specify a file for these to0 码力 | 505 页 | 878.66 KB | 1 年前3
Celery 2.5 Documentationprocessing 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 try blog/models.py The comment model looks like this: from django.db import models from django.utils.translation import ugettext_lazy as _ 2.2. Tasks 35 Celery Documentation, Release 2.5.5 class Comment(models sending a broadcast message to all the workers, the workers then keep a list of revoked tasks in memory. If you want tasks to remain revoked after worker restart you need to specify a file for these to0 码力 | 400 页 | 1.40 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













