Menene context switch ke kashewa da gaske, kuma me ya sa yake da muhimmanci?

Question

IT Interview Practice · Accepted Answer

**Context switch** shi ne kernel yana adana yanayin CPU na thread da ke gudana yanzu (registers, program counter, stack pointer) yana kuma dawo da na wani thread, don core guda ya iya raba threads da yawa. Yana faruwa a kowane preemption na scheduler, blocking syscall, ko interrupt — kuma ba kyauta ba ne.

## Inda farashin ke ɓoyewa

```text
DIRECT cost (visible, ~1–5 µs):
  save/restore registers · run scheduler logic · switch kernel stacks
  if PROCESS switch: also swap page tables (CR3) → FLUSHES the TLB

INDIRECT cost (often much larger):
  cold CPU CACHES → the new thread's data isn't in L1/L2/L3 → cache misses to RAM
  cold TLB        → address translations must be re-walked
  lost pipeline / branch-predictor state
```

Farashin **kai tsaye (direct)** ƴan microseconds ne. Farashin **na kaikaice (indirect)** — cache da TLB mai sanyi bayan switch — sau da yawa shi ne babbar bugu: thread mai shigowa yana gudana a hankali na ɗan lokaci yayin da yake sake ɗumama caches ɗinsa daga main memory (goma zuwa ɗaruruwan cycles kowane miss).

## Thread vs process switch

Canzawa tsakanin **threads na process ɗaya** ya fi arha: suna raba address space, don haka page table (da TLB, a hardware ba tare da tagged TLBs / PCIDs ba) ba sai ya canza ba. Canza **processes** ƙari yana sake loda page-table base register kuma bisa al'ada yana flush ɗin TLB — shi ya sa yake kashe ƙari.

## Me ya sa yake da muhimmanci a aikace

- **Threads da yawa sosai** → scheduler yana thrash, yana kashe cycles wajen canzawa maimakon aiki; bayan wani matsayi, threads fiye da cores *yana rage* throughput.
- Shi ne babbar hujja ga samfuran **async / event-loop** (Node, nginx, `io_uring`) da **goroutines / green threads**: sarrafa haɗi da yawa da ƴan OS threads, guje wa switch a kowane request.
- Shi ne dalilin da ya sa **CPU pinning / affinity** ke taimaka wa sabis masu kula da latency — riƙe thread a core ɗaya don adana cache ɗinsa mai ɗumi.
- Yawan context-switch na tilas (involuntary) mai yawa (ana gani a `vmstat`, `pidstat`) alama ce ta gargajiya ta lock contention ko CPU oversubscription.

## Me ya sa yake da muhimmanci

Wannan tambaya ce ta matakin senior domin tana rarrabe mutanen da suka san *kalmar* da waɗanda suka fahimci *dalilin* da ya sa take da tsada — kuma amsar gaske (gurɓatar cache/TLB, ba adana registers kaɗai ba) tana jagorantar shawarwarin gine-gine: async I/O maimakon thread-per-request, daidaita girman thread pools da yawan cores, da amfani da affinity. Yana haɗa scheduling, virtual memory, da CPU caches cikin labari ɗaya na aiki (performance).

Inda farashin ke ɓoyewa

Thread vs process switch

Me ya sa yake da muhimmanci a aikace

Me ya sa yake da muhimmanci

Tambayoyi masu alaƙa