Changes between Version 1 and Version 3 of Ticket #2614


Ignore:
Timestamp:
03/13/24 04:31:36 (9 months ago)
Author:
sm815lee@…
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2614 – Description

    v1 v3  
    66
    77[simple topology picture, please append https:/]
     8[https://trac.nginx.org/nginx/attachment/ticket/2614/vanilla_nginx_400k_conn_grpc.png]
     9[https://trac.nginx.org/nginx/attachment/ticket/2614/nginx_simple_topology.png]
    810drive.usercontent.google.com/download?id=12QLfhidHyKAiB4Z4S7WiODfNPlwdenU8&export=view&authuser=0
    911
    … …  
    1719
    1820[massif analyzer graph picture]
     21[https://trac.nginx.org/nginx/attachment/ticket/2614/nginx_memory_massif.png]
    1922[https://drive.usercontent.google.com/download?id=1FZ40HtHeWXDPFVgw9lk86Nv4AzadGo4Z&export=view&authuser=0]
    2023
    … …  
    2831
    2932So it would be very helpful to share recommendations for this issue.
     33
     34*** Here is update 2024 MAR 13th ***
     35During a recent test, we found that the connection itself doesn't bring up the memory leak issue but the gRPC stream's message does.
     36With the same number of connections, we have doubled the number of the gRPC stream's messages and it shows almost doubled memory consumption.
     37
     38[https://trac.nginx.org/nginx/attachment/ticket/2614/grpc-message-memory-ratio.png]
     39
    3040
    3141Here are the configuration files