Files

T

Software Orchestrator 5769c1cd22 Initial commit: a0_software_orchestrator v1.0

- Auto-Registration-Bug behoben (register_project/get_project_id/resolve_project Trennung)
- 25 Tests gruen (Pytest)
- block_compactor-Tool refactored (Option B: Soft-Check statt Hard-Block)
- 4 Restbaustellen gefixt
- DB-Schema: plugin_settings-Tabelle hinzugefuegt
- 3 Schattenprojekte aus DB geloescht
- Plan v3 + Refactor-Plan + Worklog dokumentiert

2026-06-16 22:13:06 +00:00

671 B

Raw Blame History

22_resource_sizing.md

Resource Sizing

Ressourcen

Runtime RAM
Runtime CPU
Build RAM
Disk
DB Size
Uploads
Indexes
Worker Load
Network

Heavy Signals

DB+Redis+Worker+Search
Vector DB
LLM/AI
Media/PDF/Office Processing
Analytics/Event DB
große Uploads

Dann Compose-first, Sizing und Backup prüfen.

Build-Risiko

Große Node/Java/Rust Builds können RAM sprengen. Strategien:

CI Image-first
Dockerfile optimieren
Build Cache
größerer Server

Output

resource_estimate:
  ram:
  cpu:
  disk:
  build_risk:
  runtime_risk:
  scaling_notes:

Stop bei AI/Search/Vector/Media/Office/Analytics ohne Sizing.

671 B Raw Blame History