You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2020/05/06 08:00:49 UTC

[GitHub] [incubator-apisix] Miss-you opened a new issue #1549: bug: Apache APISIX concurrent connection statistics implementation method is wrong

Miss-you opened a new issue #1549:
URL: https://github.com/apache/incubator-apisix/issues/1549


   ### Issue description
   
   The current statistical method of the number of concurrent connections is to count +1 when there is a new http request and -1 when processing a request, but in fact a long connection often has multiple http requests and responses.
   
   The number of concurrent connections is usually based on the nginx qos module
   
   ### Environment
   
   * apisix version (cmd: `apisix version`):
   * OS:
   
   ### Minimal test code / Steps to reproduce the issue
   1.
   2.
   3.
   
   ### What's the actual result? (including assertion message & call stack if applicable)
   
   
   
   ### What's the expected result?
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [incubator-apisix] moonming commented on issue #1549: bug: Apache APISIX concurrent connection statistics implementation method is wrong

Posted by GitBox <gi...@apache.org>.
moonming commented on issue #1549:
URL: https://github.com/apache/incubator-apisix/issues/1549#issuecomment-626477644


   I don't think it's bug, and this isn't a QPS concept either.
   please refer to https://github.com/openresty/lua-resty-limit-traffic/blob/master/lib/resty/limit/conn.md, maybe `request concurrency` is more clear. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org