Skip to content
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

Investigate recent surge in growth rate of system RAM usage #2030

Closed
bhazzard opened this issue Jan 3, 2024 · 0 comments · Fixed by #2039
Closed

Investigate recent surge in growth rate of system RAM usage #2030

bhazzard opened this issue Jan 3, 2024 · 0 comments · Fixed by #2039
Assignees
Labels
bug Something isn't working 👍 lgtm
Milestone

Comments

@bhazzard
Copy link

bhazzard commented Jan 3, 2024

We've seen a recent increase in the growth rate of system RAM usage that seemed to correspond with upgrading to Leap v5.0.0.

This shows a 90 day period for a public api server that was upgraded to Leap v5.0.0:
90 day public api v5.0.5

This shows the same 90 day period for a public api server that is still running Leap v4.0.4:
90 day public api v4.0.4

Note the difference in the rate of increase of system RAM usage between 5.0 and 4.0.

A different node operator provided this data:
Matthew
("eos-bp24" is running 4.0, "eos-peer72" is running 5.0.)

Note that the rate of increase in system RAM usage is not significantly different between 5.0 and 4.0.

So, we have 2 contrasting data points. Both show that the rate of growth of system RAM usage has recently increased. One suggests that it was caused by 5.0. The other suggests that it was NOT caused by 5.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working 👍 lgtm
Projects
None yet
4 participants