Kina ka sarrafa albarkatun kwantena (CPU da alaƙa)?

Question

IT Interview Practice · Accepted Answer

By default, containers can use **unlimited host resources** — which risks one container starving others or crashing the host. Docker lets you set **resource limits** (CPU, memory) to control consumption, important for stability and fair resource sharing in production.

## Matsala: ba-iyakacce amfani da albarkatun

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

## Saita iyakoki na alaƙa da 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
```

Memory limits (`-m`) cap usage (the container is **OOM-killed** if it exceeds the hard limit); CPU limits (`--cpus`) cap CPU usage. **Reservations** guarantee a minimum.

## Lura da gyara

```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
```

## Me ya sa yana da mahimmanci

Ganin hanya ta sarrafa albarkatun kwantena yana da mahimmanci don **gudun kwantena cikin inganci a kasua**, saboda haka ya zama sanin aiki mai daraja.

Matsal asali — by default, **kwantena na iya cinye duk albarkatun da ke samuwa akan host** — ainihin hadari ne: kwantena guda daya mai bugi ko mai aiki (mai musaye na alaƙa ko jiya da ke fice) zai iya **kashe sauran kwantena ko dugawa gida gaba** (abin alaƙa kusan karami), wanda zai mai ƙura gida.

Saita **iyakoki na albarkatun** (alaƙa da CPU) yana hana haka ta **kayyade amfani da albarkatun kwantena**, tiyata cewa kwantena guda daya ba zai kawo da wasu ko gida — wajibai ne don inganci a lokacin gudun kwantena masu yawa kowannan host (al'adin a kasua).

Ganin yadda za a saita **iyakoki na alaƙa** (kwantena yana da OOM-killed idan ya wuce iyaka mai karfi) da **iyakoki na CPU**, sanin **reservations** (tiyata mafi kareme), shine hanya da amfani a tsinkayi albarkatun da maidaidaicin bakin hannu.

Ganin yadda za a **lura da gyara** — amfani da `docker stats` don lura da amfani na gaske da saitin iyakoki daidai, ganin `OOMKilled` (kwantena da ya bugi iyaka na alaƙa) don gane matsaloli — yana da mahimmanci don saita iyakoki da dace da gaske bukatun.

Hanun jarin kwantena ne ya shafi aiki: **Kubernetes yana amfani da habibi iyakoki/limits** waɗanda suke bukatuwa don shirya da inganci, saboda haka ganin ra'ayi yana canji zuwa nofokai da aka shirya.

Tun da gudun kwantena masu yawa na bukatar hana rikici na albarkatun da amfani da wuce iyaka, kuma tun da iyakoki na albarkatun (iyakoki na alaƙa da CPU, reservations, lura) shine hanya ta kayyade kwantena da kare inganci na host, ganin sarrafa albarkatun kwantena yana da daraja, aiki mai mahimmanci ne sanin kwantena masu yawa a kasua — wajibai ne don gida mai kwantena maraya da ra'ayin da ya rataya ga nofokai na shirya kamar Kubernetes, inda nuni mai albarkatun yana tushe.

Matsala: ba-iyakacce amfani da albarkatun

Saita iyakoki na alaƙa da CPU

Lura da gyara

Me ya sa yana da mahimmanci

Tambayoyi masu alaƙa