Celery 3.1 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 887 页 | 1.22 MB | 1 年前3- Celery v4.0.1 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1040 页 | 1.37 MB | 1 年前3
- Celery v4.0.2 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1042 页 | 1.37 MB | 1 年前3
- Celery v4.1.0 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1057 页 | 1.35 MB | 1 年前3
- Celery 4.0 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1042 页 | 1.37 MB | 1 年前3
- Celery v4.2.1 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1121 页 | 1.38 MB | 1 年前3
- Celery v4.2.2 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1121 页 | 1.38 MB | 1 年前3
- Celery v4.2.0 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1110 页 | 1.36 MB | 1 年前3
- Celery v4.4.5 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1215 页 | 1.44 MB | 1 年前3
- Celery 4.4.0 DocumentationNow depends on kombu 2.5.8 Now depends on billiard 2.7.3.23 RabbitMQ/Redis: thread-less and lock-free rate-limit implementation. This means that rate limits pose minimal overhead when used with RabbitMQ/Redis0 码力 | 1185 页 | 1.42 MB | 1 年前3
共 24 条
- 1
- 2
- 3