<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap:break-word"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><p style="font-family:'helvetica Neue',helvetica;font-size:14px">Hi!</p><p style="font-family:'helvetica Neue',helvetica;font-size:14px">Just as the <a href="https://www.nginx.com/blog/socket-sharding-nginx-release-1-9-1/">article</a> says,</p><blockquote class="clean_bq" style="font-family:'helvetica Neue',helvetica;font-size:14px"><p>it can also mean that when a worker is stalled by a blocking operation, the block affects not only connections that the worker has already accepted, but also connection requests that the kernel has assigned to the worker since it became blocked.</p></blockquote><p style="font-family:'helvetica Neue',helvetica;font-size:14px">Is there such a possibility that some blocking operations in your production result in the dropping of QPS?</p></div> <br> <div id="bloop_sign_1495505450233389824" class="bloop_sign"></div> <br><p class="airmail_on">On 17 May 2017 at 19:58:37, fengx (<a href="mailto:nginx-forum@forum.nginx.org">nginx-forum@forum.nginx.org</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hello
<br>
<br>It shows the new feature reusport from v1.9.1 can increase the QPS by 2-3
<br>times than accept_mutex on and off in this article
<br><a href="https://www.nginx.com/blog/socket-sharding-nginx-release-1-9-1/">https://www.nginx.com/blog/socket-sharding-nginx-release-1-9-1/</a>. But the
<br>result is disappointed when we have the test in our production with
<br>V1.11.2.2. It don't even have the improvement but reduced, by 10%, dropped
<br>from 42K QPS(with accept_mutex off) to 38K QPS(with reuseport enabled). and
<br>it indeed reduce the latency. The two test cases have anything identicial
<br>except that the later have reuseport enabled. I wonder if I have missed
<br>some special configuration.
<br>
<br>Thanks.
<br>Xiaofeng
<br>
<br>Posted at Nginx Forum: <a href="https://forum.nginx.org/read.php?2,274281,274281#msg-274281">https://forum.nginx.org/read.php?2,274281,274281#msg-274281</a>
<br>
<br>_______________________________________________
<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">http://mailman.nginx.org/mailman/listinfo/nginx</a>
<br></div></div></span></blockquote></body></html>