refactor: rename thumbnail_rendering queue to asset_pipeline
The queue handles far more than thumbnails: OCC tessellation, USD master generation, GLB production, order line renders, and workflow renders. asset_pipeline better reflects its role as the render-worker's primary queue. Updated all references in: task decorators, celery_app.py, beat_tasks.py, docker-compose.yml worker command, worker.py MONITORED_QUEUES, admin.py, CLAUDE.md, LEARNINGS.md, Dockerfile, helpTexts.ts, test files, and all .claude/commands/*.md skill files. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -22,7 +22,7 @@ Automatisiertes Render-System für Schaeffler-Produktbilder. Kunden (intern) lad
|
||||
| `redis` | 6379 | Celery Broker |
|
||||
| `backend` | 8888 | FastAPI App (uvicorn) |
|
||||
| `worker` | – | Celery Worker, Queue: `step_processing`, concurrency=8 |
|
||||
| `worker-thumbnail` | – | Celery Worker, Queue: `thumbnail_rendering`, **concurrency=1** |
|
||||
| `worker-thumbnail` | – | Celery Worker, Queue: `asset_pipeline`, **concurrency=1** |
|
||||
| `beat` | – | Celery Beat (Scheduler) |
|
||||
| `blender-renderer` | 8100 | Blender HTTP-Service (STEP→PNG, STEP→STL) |
|
||||
| `threejs-renderer` | 8101 | Three.js/Playwright HTTP-Service |
|
||||
@@ -105,10 +105,10 @@ docker compose exec backend alembic current
|
||||
| Queue | Worker | Concurrency | Tasks |
|
||||
|---|---|---|---|
|
||||
| `step_processing` | `worker` | 8 | `process_step_file`, `render_order_line_task`, `dispatch_order_line_render` |
|
||||
| `thumbnail_rendering` | `worker-thumbnail` | 1 | `render_step_thumbnail`, `regenerate_thumbnail`, `generate_stl_cache` |
|
||||
| `asset_pipeline` | `worker-thumbnail` | 1 | `render_step_thumbnail`, `regenerate_thumbnail`, `generate_stl_cache` |
|
||||
| `ai_validation` | `worker` | 8 | Azure AI Validierung |
|
||||
|
||||
**Wichtig**: `thumbnail_rendering` läuft mit concurrency=1, weil der blender-renderer nur 1 Request gleichzeitig verarbeiten kann. Mehr parallele Requests führen zu Timeouts.
|
||||
**Wichtig**: `asset_pipeline` läuft mit concurrency=1, weil der blender-renderer nur 1 Request gleichzeitig verarbeiten kann. Mehr parallele Requests führen zu Timeouts.
|
||||
|
||||
## STEP-Processing-Pipeline
|
||||
|
||||
@@ -118,7 +118,7 @@ docker compose exec backend alembic current
|
||||
- `parsed_objects` in DB speichern
|
||||
- glTF konvertieren (falls konfiguriert)
|
||||
- Status: `processing` → queut `render_step_thumbnail`
|
||||
3. **Thumbnail** (`render_step_thumbnail` auf `thumbnail_rendering`):
|
||||
3. **Thumbnail** (`render_step_thumbnail` auf `asset_pipeline`):
|
||||
- Blender oder Three.js renderer aufrufen
|
||||
- STL-Cache erstellen: `{step_stem}_low.stl`, `{step_stem}_high.stl`
|
||||
- Status: `completed` oder `failed`
|
||||
|
||||
Reference in New Issue
Block a user