wliang368-leon opened a new issue, #14062:
URL: https://github.com/apache/apisix/issues/14062

   Hi APISIX team,
   
   I’m investigating a memory usage issue after upgrading Apache APISIX from 
3.12 to 3.18.
   
   Our main use case is LLM/AI Gateway, and we are using the ai-proxy-multi 
plugin.
   
   Environment
   
   * APISIX: 3.18
   * Previous version: 3.12
   * Deployment: Kubernetes
   * Main plugin: ai-proxy-multi
   * Traffic: production LLM traffic
   * Models/upstream endpoints: essentially unchanged before and after the 
upgrade
   
   Problem
   
   After upgrading from 3.12 to 3.18, APISIX worker memory usage gradually 
increases.
   We did not observe this behavior with the same workload on APISIX 3.12.
   
   Restarting the APISIX pods temporarily brings memory usage back down, but it 
gradually increases again.
   
   Questions
   
   1. Are there any known memory issues/regressions related to ai-proxy-multi 
between 3.12 and 3.18?
   2. Did the upstream/connection-pool handling of ai-proxy-multi change 
between these versions?
   3. Can multiple ai-proxy-multi instances/routes targeting the same upstream 
share the same keepalive connection pool?
   4. Is there any known issue where ai-proxy-multi or its upstream connection 
pools retain Lua objects/connections and cause memory to grow over several days?
   5. Are there any recommended metrics or debugging methods to distinguish:
       * Lua/worker memory growth
       * connection pool growth
       * APISIX/OpenResty memory leak
       * Linux page cache caused by log files
   6. If anyone has investigated a similar issue in APISIX 3.18, what would be 
the recommended way to isolate the root cause?
   
   I can provide configuration snippets, memory metrics, worker information, 
and relevant logs if needed.
   
   Thanks!
   
   _Originally posted by @wliang368-leon in 
https://github.com/apache/apisix/discussions/13999_


-- 
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]

Reply via email to