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
I am trying to monitor large number of devices and have additional collectors running along with the hertzbeat manager.
Hertzbeat version - 1.7.2
Tasks associated with each collector - approx 800
Collector configuration - 4 GB RAM per collector
RAM usage is between 2.8 GB to 3 GB. This is even after scheduled interval collection is complete. Heap dump suggests HashedWheelTimeout as Leak suspect similar to issue #3534
Is the high RAM usage even after collection is complete expected ? Or is the collector expected to reduce RAM usage when it is not collecting metric data ?
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
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to monitor large number of devices and have additional collectors running along with the hertzbeat manager.
Hertzbeat version - 1.7.2
Tasks associated with each collector - approx 800
Collector configuration - 4 GB RAM per collector
RAM usage is between 2.8 GB to 3 GB. This is even after scheduled interval collection is complete. Heap dump suggests HashedWheelTimeout as Leak suspect similar to issue #3534
Is the high RAM usage even after collection is complete expected ? Or is the collector expected to reduce RAM usage when it is not collecting metric data ?
Beta Was this translation helpful? Give feedback.
All reactions