Changes between Initial Version and Version 1 of Ticket #2614
- Timestamp:
- 03/06/24 08:29:42 (2 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2614 – Description
initial v1 1 1 Hello all, 2 2 3 We have a workload that the load balancer server keeps long-lived gRPC connections like common TCP servers.4 And in the client, from time to time, it sends small gRPC calls to the reverse proxy server. So we chose to make an in-house gRPC test-client program to measure CPU and memory usage of nginx with a similar workload.3 We have a workload that the load balancer server keeps long-lived gRPC-stream connections like common TCP servers. 4 And in the client, from time to time, it sends small gRPC calls to the reverse proxy server. So we chose to make an in-house gRPC-stream test-client program to measure CPU and memory usage of nginx with a similar workload. 5 5 There is a simple network topology and test environment. we have tested it using AWS EC2 VMs. 6 6 … … 21 21 Although we found some recommendations of memory management for nginx on the guide document like nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_requests 22 22 we think it's not fair that nginx costs gradual memory space on every connection during its lifespan like a tax ;) 23 And some nginx's directives, keepalive_requests, and keepalive_time, didn't even affect gRPC connections.23 And some nginx's directives, keepalive_requests, and keepalive_time, didn't even affect gRPC-stream connections. 24 24 25 25 Currently, we don't even know whether this is what Nginx is originally intended for or not.
