# 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.