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
This commit is contained in:
@@ -0,0 +1,55 @@
|
||||
# 22_resource_sizing.md
|
||||
|
||||
# Resource Sizing
|
||||
|
||||
## Ressourcen
|
||||
|
||||
```text
|
||||
Runtime RAM
|
||||
Runtime CPU
|
||||
Build RAM
|
||||
Disk
|
||||
DB Size
|
||||
Uploads
|
||||
Indexes
|
||||
Worker Load
|
||||
Network
|
||||
```
|
||||
|
||||
## Heavy Signals
|
||||
|
||||
```text
|
||||
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:
|
||||
|
||||
```text
|
||||
CI Image-first
|
||||
Dockerfile optimieren
|
||||
Build Cache
|
||||
größerer Server
|
||||
```
|
||||
|
||||
## Output
|
||||
|
||||
```yaml
|
||||
resource_estimate:
|
||||
ram:
|
||||
cpu:
|
||||
disk:
|
||||
build_risk:
|
||||
runtime_risk:
|
||||
scaling_notes:
|
||||
```
|
||||
|
||||
Stop bei AI/Search/Vector/Media/Office/Analytics ohne Sizing.
|
||||
Reference in New Issue
Block a user