Me ya sa haɗe-haɗen Nginx za su ƙare alhali CPU bai cika ba?

Question

IT Interview Practice · Accepted Answer

Haɗuwa na iya riƙe albarkatu yayin jira ko da amfani da CPU ya yi ƙasa. Da farko gano iyakar da aka kai maimakon ɗauka cewa na'urar tana buƙatar ƙarin ƙarfin sarrafawa.

## Ƙirga bangarori biyu na buƙatar proxy

```text
Client -- socket A --> Nginx -- socket B --> Backend
```

Buƙatar HTTP/1.x da ake turawa ta proxy na iya amfani da haɗuwar client ɗaya da wata ta upstream. Idan backend ya tsaya, duka biyu za su iya ci gaba da kasancewa a cike. `worker_connections` ya haɗa da upstream connections, don haka ƙimarsa ba kawai adadin masu amfani da ake iya ɗauka ba ce.

## Mayar da kuskuren zuwa abin bincike

- `worker_connections are not enough`: duba iyakar haɗe-haɗe da aka saita ga kowane worker da waɗanda suke yanzu.
- `Too many open files`: duba ainihin iyakar file descriptors na worker. Descriptor wata alamar tsarin aiki ce da ake amfani da ita ga sockets da fayiloli.
- Ƙaruwa a lokacin amsar upstream: binciki aikin backend da yake riƙe haɗe-haɗen.

A misali, buƙatu 1,000 masu aiki lokaci guda ta proxy na iya buƙatar kimanin sockets 2,000 a bangarorin biyu. Wannan ba dabarar ƙididdigar girman tsarin ba ce: HTTP/2, sake amfani da keepalive da haɗe-haɗe marasa aiki suna sauya alaƙar.

## Ƙara ƙarfin ɗauka bayan gano dalili kawai

Da farko gyara aikin backend da ya tsaya ko iyakance buƙatun da suke jira. Idan zirga-zirga mai lafiya ta wuce iyakoki, daidaita saitunan workers, process limits da memory, sannan yi load test. Tabbatar cewa successful throughput da latency sun inganta, ba kawai ƙyale queue mai tsawo ba.

[Takardun hukuma](https://nginx.org/en/docs/ngx_core_module.html#worker_connections).

Ƙirga bangarori biyu na buƙatar proxy

Mayar da kuskuren zuwa abin bincike

Ƙara ƙarfin ɗauka bayan gano dalili kawai

Tambayoyi masu alaƙa