-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when using "resty.limit.req" to control rate, actual request processing rate might exceed configured rate. #40
Comments
@NagamineLee You should use |
sorry, this is a mistake. Actually I used |
I'm in the same boat as you; i test ngx_http_limit_req_module is OK |
@NagamineLee Please provide a minimal and self-contained example that we can easily reproduce the problem on our side. We don't want to guess. |
@NagamineLee Also detailed steps to reproduce the problem and your actual output in each step would be very useful. |
http {
limit_req_zone $uri zone=one:10m rate=1000r/s;
server {
location /limit-req {
access_by_lua_block {
local limit_req = require "resty.limit.req"
local lim, err = limit_req.new("my_limit_req_store", 100, 0)
...
if delay >= 0.001 then
--ngx.sleep(delay)
end
}
...
}
}
}
When using jmeter(threads=400, interval=300s) to simulate the stress test, jmeter test results show that actual request processing rate(hearly 1000r/s) has exceeded configured rate(100r/s).
even though start delay processing, the result is same.
The text was updated successfully, but these errors were encountered: