31
22.1 Legacy Series / Re: Memory getting saturated
« on: February 16, 2022, 09:58:28 pm »
I'm having similar issues.
Let me start with this though... I don't typically recommend enabling netdata unless it is necessary. At my prior employer we had so many problems with netdata memory leaks that we decided to disable it except when doing diagnostic testing. I don't know if that will solve your problem, but it definitely won't solve mine.
For me, in top unbound wants to use 9GB of RAM. This is a business with about 40 bitcoin miners on it. They all point to the same place, and I have no explanation for how/why unbound would need that much RAM. I haven't done anything crazy with unbound to explain this behavior.
I got an alert that my RAM is now 96% full (system has 8GB of RAM) and is up to date.
Anyone aware of any memory leak or other issue with Unbound? I'm tempted to restart the service just to hopefully get unbound under control. But ideally I like to troubleshoot the problem and fix it permanently rather than a temporary fix like restarting a service. Notice in the screenshots that its even started using swapspace. I've ordered more RAM for this box so it can be upped to 16GB, but I got this strong suspicion that unbound will eventually fill that up too.
Let me start with this though... I don't typically recommend enabling netdata unless it is necessary. At my prior employer we had so many problems with netdata memory leaks that we decided to disable it except when doing diagnostic testing. I don't know if that will solve your problem, but it definitely won't solve mine.
For me, in top unbound wants to use 9GB of RAM. This is a business with about 40 bitcoin miners on it. They all point to the same place, and I have no explanation for how/why unbound would need that much RAM. I haven't done anything crazy with unbound to explain this behavior.
I got an alert that my RAM is now 96% full (system has 8GB of RAM) and is up to date.
Anyone aware of any memory leak or other issue with Unbound? I'm tempted to restart the service just to hopefully get unbound under control. But ideally I like to troubleshoot the problem and fix it permanently rather than a temporary fix like restarting a service. Notice in the screenshots that its even started using swapspace. I've ordered more RAM for this box so it can be upped to 16GB, but I got this strong suspicion that unbound will eventually fill that up too.