Nobilta commented on issue #10349: URL: https://github.com/apache/apisix/issues/10349#issuecomment-1776521774
> > Stage information: > > > > 1. From the current perspective of slab leaks in Linux, it cannot be concluded that APISIX also has memory leaks. > > 2. APISIX's radixtree-based route matching is completely in user mode and has nothing to do with the kernel data structure radix_tree_node. > > 3. APISIX is implemented based on NGX. Because ngx has its own memory management, from the perspective of the operating system, the ngx memory has not been released. > > 4. User feedback The reason why 3.3 APISIX is ok is that the operating system kernel is different. 3.3 runs on the tlinux kernel. > > > > further processing > > > > 1. Wait for the user to switch to tlinux and retest. > > After upgrading the kernel to 5.4.119-19.0009.32, the phenomenon is the same as before. The openresty worker memory keeps growing after receiving traffic. In the same environment as APISIX 3.3, using the same plug-in configuration (different data plane), version 3.5 has a memory leak problem, but version 3.3 works normally. <img alt="357c914aafdb1ed9d33a33ebf0243e6" width="1817" src="https://user-images.githubusercontent.com/59631965/277531823-2dd0aca8-5a03-442e-8727-f93f296b2413.png">  According to the memory data of the last dump, the largest address space occupied after string processing is the upstream node information related to the use of the traffic-split plugin.The upstream node information that appears in the dump file is all part 1 in the figure, and the node 2 almost does not exist in the dump file. so we suspect whether it is related to the modification of the traffic-split plugin in version 3.5.  -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
