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

High loadavg when settings page is open #9

Closed
daneedk opened this issue Jan 31, 2018 · 3 comments

Comments

Projects
None yet
1 participant
@daneedk
Copy link
Owner

commented Jan 31, 2018

Fire69 wrote:

Also, it seems like my loadavg shoots through the roof (goes from ~0.4 to ~3) when the settings page is open.
Am I the only one?

@daneedk

This comment has been minimized.

Copy link
Owner Author

commented Jan 31, 2018

Fire69 wrote:

DaneeDeKruyff said:
Thanks!

I can't say I see an impact on the loadavg myself, but I've cleared my history yesterday and only log when in Armed mode so not much entries yet. I can imagine having a large history can put some load on Homey when you're in the settings page as that is retrieved every second.

Same settings here, so I guess that can't be the problem :)

[edit]
Did some more testing, the high load is indeed caused by the automatic refresh, even when the state is disarmed and no new entries are being logged.
When I disable the automatic refresh the loadavg slowly goes back to ~0.3

[edit2]
After removing the history enabling auto refresh doesn't change the loadavg anymore.
Maybe there's another way to do the refresh which doesn't stress the cpu as much?
Or make it so that we can input the refresh interval ourselves to set it to 5 or 10 sec?

@daneedk

This comment has been minimized.

Copy link
Owner Author

commented Jan 31, 2018

Made a change so the history is only retrieved from Homey when the Dashboard tab is selected.

Will add a button to do a manual refresh when auto refresh is off.

@daneedk

This comment has been minimized.

Copy link
Owner Author

commented Feb 2, 2018

Version 0.1.8 containing the changes is published

@daneedk daneedk closed this Feb 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.