I noticed my C8's cpu got below 170k today, so I shutdown/power cycled.
Is this memory loss inevitable, and should I put the hub on a routine restart?
Memory loss (memory leaks) will occur. How fast will depend on what apps and drivers you use. I have a rule setup on my hub that will reboot it during the night if it goes below a certain level at any point during the day. This works great for my needs.
2 Likes
This is my C-8 after running for 22 days.
I do have a rule to reboot the hub if free memory drops below 130M. It has never been triggered. But I agree with @Sebastien that it depends on the exact mix of apps and drivers on your hub.
4 Likes
Do you and @Sebastien feel that running the @thebearmay 's driver adds to the problem, as far as memory goes, or is it a non issue?
Cannot really say that it is inevitable as I suppose it depends on the “load” on your HE. I have somme very hungry and “chatty” apps running such as Envisalink and Ecobee Suite. I also have frequent polling on my TPLink switches. That being said, as you can see from my screenshot of my Hub Status Dashboard, I am currently able to get around 30 days of operation before my hub auto reboots (at 175,000 kb). This has not always been the case. With some former versions of the firmware, my hub would reboot about once every 10-15 days or so. At any rate, firmware updates were coming out so frequently from the HE staff that even this was not a problem (as long as you made the decision to download each update, some of you may decide to not mess with a stable system as long as it works for you in your use case). I am one who tends to update even when my system is working just to keep up. Fortunately, for me, without any changes to my apps (even with adding many many more apps and using RM extensively), in my case, my hub seemed to run more efficiently for some reason to the point where I am getting over 30 days use before my reboot threshold. As usual, YMMV.
As you can see, the free memory on my system seems to drop very gradually. As you cannot see, given the start point of the graph, there is a relatively sharp drop off right after rebooting, after which the slope of the graph gradually gets flatter. Not sure this answers your question (in fact I know it does not, lol) but along with the experience of others, our cumulative experiences may give you a better idea of what can be expected. Hope this helps.
2 Likes
There is a fairly easy way to test that theory. There is a node-Red flow that can capture most of the same performance data. Someone could uninstall the driver and just run that and see if it changes their memory time.
I wouldn't expect it to make to much of a difference though. I suspect it is really all about the quantity of work you are simply asking the hub to do with the number of devices and integrations you have like others have said. Some integrations like Ecobee suites gets very robust to it's own detriment and can cause some users issues.
1 Like
I would investigate (by screening the logs for warnings, errors and hyperactive apps and drivers) and address any issues first, before I would consider scheduling reboots. I've never had to monitor my production hub's memory because my hub never had performance issues that I couldn't trace to an app or device that was misbehaving, or I accidentally misconfig.
2 Likes
Here is the graph of my setup over the last 30 days.
The yellow graph is my dev hub and the green graph is my prod hub. You can see in both cases the hub will drop very quick after reboot, and then settle in and gradually decrease over time after that first 12-24 hour period. The sudden drops after that are when I had a Home server issue and InfluxDB Logger was holding records until i got it back up. That is a great example of an app having external connectivity problems and it causing issues with the hub. You can actually see with the drop just after 8/1 once I recovered the database connectivity Memory usage started dropping at a normal pace again. I really think allot of resource problems are LAN/Connectivity related.
I do think it is a trade off with do you want the functionality or do you want it to run and use resources very lightly.
3 Likes
I do have the Envisilink application, which I find helpful.
That's about it though, as far as integrations.
I do have an Aeotec home energy monitor doing 5 second updates.
Plus, a couple of SmartThings arrival sensors updating 20 seconds each.
More than a few Hue motions.
4 3R temp/humidity sensors...they really aren't that bad.
Non issue for me. On every hub that I've used it on.
1 Like
Thanks everyone.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
