-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Description
Hi FreeSWITCH team,
I'm currently running a sustained load test on FreeSWITCH and have noticed some memory behavior that I would like to clarify or get help with.
Test Environment:
- FreeSWITCH version: 1.10.12
- OS: Debian 11
- Deployment: Docker container (to easily monitor CPU & RAM)
- System Resources: 8-core CPU, 16 GB RAM
- Load Test Tool: sipp
- Traffic Pattern: ~40 CPS, ~400 concurrent calls
- Test Duration: continuously running for nearly a month
Observations:
-
When I do not set any memory limit, the system's RAM usage gradually increases over time due to caching — eventually consuming most of the RAM. However, FreeSWITCH appears to remain stable, and the system continues to function normally.
-
When I monitor RAM usage within the container, I observe:
-
CPU usage stays stable and flat over time.
-
RAM usage, however, gradually increases and does not appear to be released. Even though the growth is slow, it concerns me that over a long enough duration, RAM could eventually fill up and potentially trigger an OOM (Out of Memory) event.
I'm currently testing with a memory limit of 2GB for the container to observe what will happen once that threshold is reached, but it’s progressing slowly.
My Question:
Is this slow memory increase under long-term high call load expected behavior (perhaps due to caching, session tracking, or module behavior)?
Could this lead to memory leaks or an OOM situation over time?
Are there any recommended configurations or tuning parameters to mitigate or monitor this better?
Any insight or suggestions would be greatly appreciated.
Thanks in advance for your support!

