I am not currently using any bandwidth limiting features so I can't comment on how it is done currently. However in the past I use the one built into Nginx and tested it with a download manager. My recollection is you could open more streams but the net effect was the download stayed at the same rate. I was impressed. I have gone to http2, so I don't know if the rate limiting features are still valid.
I have big data storage, some clients upload files to it, some download, some clients might upload a lot of small files in 100-200 parallel connections, but using only 20-30 mbit/s bandwidth, some clients can put big files in 10 parallel connections but using - 3Gbit/s bandwidth. The same situation with download. So, the first situation is normal behavior and I can't afford to limit connection number per IP, in the second case it's bandwidth overload, but I can't limit bandwidth per IP, because <a href=""background:transparent;margin-top:0pt;margin-bottom:0pt;color:rgb( 74 , 110 , 224 )" href="http://nginx.org/ru/docs/http/ngx_http_core_module.html#limit_rate" class="gmail-_e75a791d-denali-editor-page-rtfLink">http://nginx.org/ru/docs/http/ngx_http_core_module.html#limit_rate"> limit_rate</a> directive is working per request only. In general case, I just need to limit bandwidth from 1 IP, independently how many parallel TCP connections per IP used by client 10 or 100. пн, 11 нояб. 2019 г. в 20:06, Peter Booth <[email protected]>:
Best Regards Kostiantyn Velychkovsky | ||
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
