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

significantly increased memory usage after upgrade to Gluon v2020.1.x #2032

Closed
rotanid opened this issue May 25, 2020 · 1 comment · Fixed by #2036
Closed

significantly increased memory usage after upgrade to Gluon v2020.1.x #2032

rotanid opened this issue May 25, 2020 · 1 comment · Fixed by #2036
Assignees
Labels
0. type: bug This is a bug 0. type: regression 1. severity: blocker This issue/pr is required for the next release
Milestone

Comments

@rotanid
Copy link
Member

rotanid commented May 25, 2020

After updating from v2019.1.2 to v2020.1.2 memory usage increased.
The increase in our network is from average ~60% to ~70% on an idle node and at least 5% more on an active node. (with 32M memory)
On devices with only 32M memory, this leads to frequent reboots.
On devices with more memory, the increase can mostly also be seen but is not problematic.

Our firmware for these devices did not change in other ways with this Gluon version bump which could affect the memory usage.

please find attached the memory graphs of 4 32M devices and 2 64M devices before and after the firmware upgrade.

memory_v202012_18a6f7c5cdb6_841v11
memory_v202012_18a6f7c5c3bc_841v11
memory_v202012_18a6f7c5aaec_841v11
memory_v202012_60e3275773ac_841v9
memory_v202012_ec086ba4d066_1043v3
memory_v202012_18d6c75152c2_1043v4

as far as i know, others also observed the issues as reported on the Gluon IRC channel for weeks.

@rotanid rotanid added this to the 2020.2 milestone May 25, 2020
@rotanid rotanid added the 1. severity: blocker This issue/pr is required for the next release label May 25, 2020
@neocturne neocturne self-assigned this May 25, 2020
@rotanid
Copy link
Member Author

rotanid commented May 30, 2020

i can confirm that #2036 fixes the reported issue, 9 of our 10 test devices have an uptime of around 2 days by now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. type: bug This is a bug 0. type: regression 1. severity: blocker This issue/pr is required for the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants