Kepiye carane ngelola sumber daya kontainer (CPU lan memori)?

Question

Accepted Answer

Kanthi standar, kontainer bisa nggunakake **sumber daya host tanpa batas** — sing ndudut risiko siji kontainer nyuda sumber daya kontainer liyane utawa nabrak host. Docker ngidini sampeyan nyetel **batasan sumber daya** (CPU, memori) kanggo kontrol konsumsi, penting kanggo stabilitas lan paagi adil nggunakake sumber daya ing produksi.

## Masalah: panggunaan sumber daya tanpa batas

```text
BY DEFAULT a container can consume ALL available host CPU and memory:
  → a buggy/busy container (memory leak, runaway loop) can starve other containers
    or crash the entire host (out of memory)
→ In production (multiple containers per host), LIMIT resources to isolate them.
```

## Nyetel batasan memori lan CPU

```bash
# memory limits
docker run -m 512m myapp              # hard limit: 512 MB (container killed if exceeded — OOM)
docker run -m 512m --memory-reservation 256m myapp   # soft limit + hard limit

# CPU limits
docker run --cpus="1.5" myapp         # limit to 1.5 CPU cores
docker run --cpu-shares=512 myapp     # relative weight (priority under contention)
```

```yaml
# in docker-compose.yml (or for orchestrators)
services:
  app:
    deploy:
      resources:
        limits:    { cpus: '1.5', memory: 512M }   # maximum
        reservations: { cpus: '0.5', memory: 256M } # guaranteed minimum
```

Batasan memori (`-m`) tutup panggunaan (kontainer bakal **dimateni OOM** yen lampas batas keras); batasan CPU (`--cpus`) tutup panggunaan CPU. **Reservasi** njamin minimum.

## Ngetung lan nyetel ulang

```text
✓ docker stats → live CPU/memory usage per container (to right-size limits)
✓ Set limits based on the app's actual needs (measure, then add headroom)
✓ OOMKilled (in docker inspect) → the container hit its memory limit → raise it or fix a leak
✓ Orchestrators (Kubernetes) use requests/limits similarly — essential for scheduling
```

## Mengapa kuwi penting

Ngerteni manajemen sumber daya kontainer penting kanggo **nglakokake kontainer kanthi andal ing produksi**, dadi iku ilmu operasional sing regane.

Masalah utama — kanthi standar, **kontainer bisa nggunakake kabeh sumber daya host sing ana** — iku risiko nyata: siji kontainer sing cacat utawa sibuk (kanthi memory leak utawa proses mangkal) bisa **nyuda kontainer liyane utawa tabrak kabeh host** (mati memori), nggawekake host ora stabil.

Nyetel **batasan sumber daya** (memori lan CPU) nyegah iki kanthi **ngisolasi panggunaan sumber daya kontainer**, ndedel siji kontainer ora bisa tabrak liyane utawa host — penting kanggo stabilitas nalika nglakokake akeh kontainer saben host (lumrah ing produksi).

Ngerteni carane nyetel **batasan memori** (kanthi kontainer dimateni OOM yen lampas batas keras) lan **batasan CPU**, plus **reservasi** (njamin minimum), iku mekanisme praktis kanggo kontrol lan paagi adil nggunakake sumber daya.

Nanggap carane **ngetung lan nyetel ulang** — nggunakake `docker stats` kanggo mirsani panggunaan nyata lan ukuran batasan lagi, ngakoni `OOMKilled` (kontainer nekat batasan memori) kanggo dikenali masalah — penting kanggo nyetel batasan pas karo kabutuhan nyata.

Iku uga nyambung karo orkestrasyon: **Kubernetes nggunakake permintaan/batasan sumber daya padha** sing penting kanggo jadwal lan stabilitas, dadi ngerti konsep iku mindhah menyang lingkungan orkestrasyon, kayata Kubernetes, ing ngendi spesifikasi sumber daya dadi dhasar.

Amerga nglakokake akeh kontainer kanthi andal mbutuhake nyegah pasulayan sumber daya lan konsumsi mangkal, lan merga batasan sumber daya (tutup memori lan CPU, reservasi, ngetung) iku mekanisme kanggo ngisolasi kontainer lan ngelindungi stabilitas host, ngerti manajemen sumber daya kontainer iku ilmu regane, praktis-penting kanggo pasang kontainer produksi — butuh kanggo host akeh-kontainer stabil lan konsep sing langsung kalanjut menyang lingkungan orkestrasyon kayata Kubernetes, ing ngendi spesifikasi sumber daya dadi fundamental.