bryancall commented on issue #9940: URL: https://github.com/apache/trafficserver/issues/9940#issuecomment-4828019660
I am closing this as a stale support question. This issue does not include the Apache Traffic Server version, the records configuration in use, or steps to reproduce, so the growing memory cannot be diagnosed from what is here. Process memory growth while serving large objects can come from several places (for example proxy buffering of in-flight transactions, connection counts, or allocator arena retention) that are unrelated to the RAM cache and disk cache being disabled. If this is still reproducible on a current release, please open a new issue with the exact version, your full configuration, the number of concurrent connections, and ideally a heap profile (for example from jemalloc) so we can investigate a specific cause. -- 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]
