<div dir="ltr"><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)">I suspect nginx' team chose this value for the very reason it was adapted to the use of Apache (remember that nginx is, since its beginning, largely used as a reverse Web proxy in front of Apache farms).<br></div><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)">I guess the intent here is to probably mimic Apache behavior by default so adoption of that technology is eased.<br><br></div><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)">In the Apache world, long-lasting connections may result in resource starvation, since 1 connection = expensive resources allocated. Thus, you can quickly end-up with a few (relatively and even infrequently) active clients saturating a Web server machine, leaving no spots free for newcomers, especially nowadays with multithreaded/processed browsers.<br></div><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)">Recycling connections often is an attempt at fighting that.<br><br></div><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)">Unless I am overlooking something, there seems not to have any technical ground for such a limit to be pertinent with nginx.<br></div><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)"><br></div><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)">As debated in the past on this ML (and at the 1st nginx conference), some other default values might not be right anymore, but changing default value might silently break backwards-compatibility with setups which do not comply with the new defaults. History repeatedly shows that changing old defaults and even deprecating the use of rotten algorithms is faced with huge resistance. IE6? SSLv3? RC4?, HTTP/1.0? Amongst many others...<br></div><div class="gmail_default" style="font-size:small;color:rgb(51,51,153)">Thus the nginx team position has (so far?) been to never touch the built-in defaults (and neither maybe the default nginx.conf? I have not checked that) and let people override them through configuration.<br></div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><font size="1"><span style="color:rgb(102,102,102)">---<br></span><b><span style="color:rgb(102,102,102)">B. R.</span></b><span style="color:rgb(102,102,102)"></span></font></div></div>
<br><div class="gmail_quote">On Wed, Mar 8, 2017 at 2:21 AM, Tolga Ceylan <span dir="ltr"><<a href="mailto:tolga.ceylan@gmail.com" target="_blank">tolga.ceylan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Does anybody have any history/rationale on why keepalive_requests<br>
use default of 100 requests in nginx? This same default is also used in<br>
Apache. But the default seems very small in today's standards.<br>
<br>
<a href="http://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_requests" rel="noreferrer" target="_blank">http://nginx.org/en/docs/http/<wbr>ngx_http_core_module.html#<wbr>keepalive_requests</a><br>
<br>
Regards,<br>
Tolga<br>
______________________________<wbr>_________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/<wbr>mailman/listinfo/nginx</a><br>
</blockquote></div><br></div></div>