-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak when using proxy #51
Comments
I'm not convinced that the memory is indeed leaking. In order to archive decent performance, the socket buffers per connection have to be quite large. Some megabyte per connection are reasonable. The total memory required for all sockets on a medium load can easily top multiple gigabytes. |
ivan4th
added a commit
that referenced
this issue
Jan 6, 2021
Related to #51 (but also need to kill proxy sessions together with flows)
ivan4th
added a commit
that referenced
this issue
Jan 6, 2021
Related to #51 (but also need to kill proxy sessions together with flows)
Merged
The leak is no longer observed as of v1.1.4 (after #67 was merged before an earlier release) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's a memory leak in UPG when using proxy, possibly mostly for non-stitched TCP connections.
The leak is not visible in
show memory
, but vpp RSS keeps increasing.It is likely related to SVM FIFOs being not properly freed.
Below is a flame graph constructed from page fault tracing with perf (based on [1]).
![Flame Graph](https://user-images.githubusercontent.com/190448/103213588-352eb780-491f-11eb-9c8e-aa8ef32ec9ce.png)
[1] http://www.brendangregg.com/FlameGraphs/memoryflamegraphs.html
The text was updated successfully, but these errors were encountered: