Changes between Version 1 and Version 2 of Ticket #2293, comment 7
- Timestamp:
- 12/14/21 15:48:33 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2293, comment 7
v1 v2 1 1 Setting keepalive_requests to 1000 actually improves a lot. Memory does stabilized after couple hours with same traffic rate. 2 2 3 The Client side starts with 4 connections and send requests using the round-robin. We used to set keepalive_request to 10000 to match client side setting. Because if Nginx release the connection when max request is hit, Client side receives a 503 (while using the expired connection). In order to avoid 503, we set client side max request per connection also to 10000. So that client disconnect first to avoid 503. Any suggestion how to handle this? Default 1000 is a little under traffic load.3 The Client side starts with 4 connections and send requests using the round-robin. We used to set keepalive_request to 10000 to match client side setting. Because if Nginx release the connection when max request is hit, Client side receives a 503 (while using the expired connection). In order to avoid 503, we set client side max request per connection also to 10000. So that client disconnect first to avoid 503. Any suggestion how to handle this? Default 1000 is a little low under traffic load. 4 4 5 5 We don't have any other load_module. ''aio on;, aio threads;, aio_write on'';are not used in nginx.conf
