
Priority Queues
- 5 installs
- 1 repo stars
- Updated March 10, 2026
- davidcastagnetoa/skills
Set up separate Celery priority queues (realtime, gpu, cpu, async) with dedicated workers so latency-critical tasks are not blocked by batch jobs.
About
Guides splitting a Celery task pipeline into four priority queues with dedicated workers to protect latency SLOs. A developer uses it when critical low-latency tasks compete for workers with slower batch or audit work.
- Four queues (realtime/gpu/cpu/async) each with its own SLO and dedicated workers
- GPU queue runs one process per GPU; monitor queue depth in Flower and Grafana
Priority Queues by the numbers
- 5 all-time installs (skills.sh)
- Ranked #876 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davidcastagnetoa/skills --skill priority_queuesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 1 |
| Last updated | March 10, 2026 |
| Repository | davidcastagnetoa/skills ↗ |
What it does
Set up separate Celery priority queues (realtime, gpu, cpu, async) with dedicated workers so latency-critical tasks are not blocked by batch jobs.
Files
priority_queues
Colas de prioridad separadas garantizan que las tareas críticas de baja latencia (liveness) no compiten por workers con tareas menos urgentes (auditoría, análisis batch).
When to use
Usar para segregar todas las tareas del pipeline KYC por nivel de urgencia.
Instructions
1. Definir 4 colas en la configuración de Celery:
realtime: liveness, captura (SLO < 1s).gpu: face_match, deepfake detection (SLO < 2s).cpu: OCR, document processing (SLO < 3s).async: auditoría, notificaciones, analytics (SLO < 30s).
2. Asignar tareas a colas con el decorador: @app.task(queue='gpu'). 3. Arrancar workers dedicados: celery worker -Q realtime --concurrency=4 -P prefork. 4. Asignar más workers a colas críticas. 5. Configurar task_routes en la configuración de Celery para enrutamiento automático.
Notes
- Workers de cola GPU deben tener acceso a la GPU:
-P solo --concurrency=1(un proceso por GPU). - Monitorizar la profundidad de cada cola en Flower y Grafana.
List_Agents.md
list_skills.md
CLAUDE.md
Agents.md
.DS_Store