Yi kasafin soket ɗin proxy na NGINX kafin ka ƙara worker_connections
Haɗin proxy yakan yi amfani da soket ɗin abokin ciniki da na upstream; bambanta iyakar haɗin worker da iyakar bayanin fayil na sabis ɗin.
Haɗin proxy mai tsawo yakan riƙe soket biyu: na abokin ciniki da na upstream. worker_connections yana ƙididdige ɓangarorin biyu. Don haka ninka shi da worker_processes ba ya ba da alkawarin ƙarfin aiki ga masu amfani da proxy.
Lokacin da haɗe-haɗe suka kasa, bi iyakar da aka bayar:
| Shaida | Saiti ko yanayin tsari da za a duba |
|---|---|
| ƙarewar worker_connections | Kasafin haɗin worker, gami da soket ɗin upstream |
| Saƙon tsarin aiki “Buɗaɗɗun fayiloli da yawa” | Iyakar bayanin fayil da ainihin tsarin sabis ɗin ke gado |
Soket ɗin saurara, logu da sauran buɗaɗɗun fayiloli ma suna cinye bayanai. Sake amfani da haɗe-haɗe da gaurayar zirga-zirga suna canza dangantaka tsakanin masu amfani da soket ɗi.
worker_rlimit_nofile yana daidaita iyakokin worker bisa izinin muhalli. Ƙungiyar systemd na iya saita LimitNOFILE; ulimit a cikin harsashi mai mu'amala ba ya canza sabis ɗin da ke gudana.
Yi girman iyakoki bisa nauyin aiki, kuma duba wanda ke cinye su. Abokan ciniki da ba a yi tsammani ba ko haɗe-haɗen upstream da ke kasawa akai-akai na iya ƙare kasafin da ya isa a baya. Yawan tsari ko iyakar ƙwaƙwalwar ajiya ba ya gyara ƙarancin bayanai.