-
Notifications
You must be signed in to change notification settings - Fork 6.1k
ebpf.plugin: rework memory #19844
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
ebpf.plugin: rework memory #19844
Conversation
This pull request has been mentioned on Netdata Community Forums. There might be relevant details there: https://community.netdata.cloud/t/mem-cachestat-ratio-doesnt-work-after-upgrading-netdata/7345/3 |
a5a213e
to
7884d46
Compare
3bb8cda
to
8fc84b5
Compare
46b67a9
to
82fb8fc
Compare
…implifying this PR
… memory used to store data
…fix from previous commit
82fb8fc
to
409fe31
Compare
I rebased the PR to verify no changes were introduced after the latest commits. This PR has been running successfully for four days without any issues. After completing one final test with the most recent commits, it will be marked as ready for review. |
(cherry picked from commit 12e830a)
(cherry picked from commit 12e830a)
Summary
This is the last PR before move integration from ebpf.plugin to apps.plugin and cgroup.plugin.
It address some SIGABRT and SIGSEGV identified with code allocation. On all scenarios where it was tested, I could not observe more the issues after the development finished.
Test Plan
Additional Information
This PR was tested on:
For users: How does this change affect me?
Describe the PR affects users: - Which area of Netdata is affected by the change? ebpf.plugin - Can they see the change or is it an under the hood? If they can see it, where? Plugin is going to need less memory. - How is the user impacted by the change? A more stable plugin. - What are there any benefits of the change? Plugin using less memory and without some ancient issues.