Use case: Large uploads (hundreds of megabytes to tens of gigabytes) where
nginx is serving as a reverse proxy and load balancer. The upstream servers
can get bogged down, and when they do, they apply backpressure by responding
with 503 status code.
Problem: Naively implemented, the client sends t
correction.. if i count with
ss -l -t |grep http | wc -l
we have around 58340 listening sockets.. at least on that machine..
On Fri, Apr 30, 2021 at 8:27 AM Charlie Kilo wrote:
> Thanks a lot for the hints so far.. to provide the further info and answer
> the questions..
>
> getconf ARG_MAX sho
