-
-
Notifications
You must be signed in to change notification settings - Fork 7
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 usage buildup #78
Comments
I can 100% confirm this. I noticed it happened as well & have not been able to figure out why. For now, I decided to just set a fairly low memory limit and let it get occasionally OOMKilled. Would strongly appreciate if somebody could investigate |
Not sure, but first thing that comes to mind is the logs that gets outputted every time that TTL controller is triggered. Maybe this article can help https://www.codereliant.io/memory-leaks-with-pprof/ |
Hi, nice spotted @MarcoipPolo I faced this a while ago, unfortunately i did not raised here nor documented the way I profile the code 😢 . BTW I am really grateful with @TwiN for open sourcing this project In any case the bottom-line of the research is:
My solution at the time was to add some sort of filter like
FYI I am not a golang expert |
I have also added pprof behind a gate
|
I suspect your fix may just hide the memory leak since more resources are skipped 😔 |
Describe the bug
After running the deployment for some time i noticed that it uses more and more memory as the deployment lives. This should not happen.
What do you see?
What do you expect to see?
Memory usage stabilizes on a certain point
List the steps that must be taken to reproduce this issue
Version
0.2.0 version of helmchart
Additional information
No response
The text was updated successfully, but these errors were encountered: