You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Netdata users can have multiple netdata parents in their network. So, they can add as many parents as needed to have long retention. Thankfully netdata.cloud can utilize them all, transparently.
But how many children a parent can sustain and what cpu, memory and storage requirements each parent should have?
On the parent each child has its own thread. So, the parent should be able to utilize all the available CPU cores. I tested this and I found that each child thread on the parent uses about 1-2% CPU utilization, so probably 50 children per core on the parent are what someone could expect.
What about memory and storage?
Any bugs that prevent the parent to scale?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Goal: A parent with 1 year data retention.
Netdata users can have multiple netdata parents in their network. So, they can add as many parents as needed to have long retention. Thankfully netdata.cloud can utilize them all, transparently.
But how many children a parent can sustain and what cpu, memory and storage requirements each parent should have?
On the parent each child has its own thread. So, the parent should be able to utilize all the available CPU cores. I tested this and I found that each child thread on the parent uses about 1-2% CPU utilization, so probably 50 children per core on the parent are what someone could expect.
What about memory and storage?
Any bugs that prevent the parent to scale?
Beta Was this translation helpful? Give feedback.
All reactions