I am wondering if anyone still uses this plugin
Announcement
Collapse
No announcement yet.
Anyone still use this plugin?
Collapse
X
-
Guest
-
Originally posted by Blade View PostIt used to be run in HS3 to lower the memory the HS3 process used to take - things have likely come a long way since then and I am wondering if anyone is running it in HS4 and if it makes a difference
I've just installed your plugin now and will let you know if it helps 👍
- Likes 1
Comment
-
I set it up on my HS3 system a few years ago. My memory sits wonderfully low. I have an event run each night @1:00am. Perhaps I don't need it, but ...HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.
Comment
-
Originally posted by Tillsy View Post
Yes and no - a bunch of us (at least via Facebook groups, talking with developers, etc) have had an ongoing network resource problem. eg if you add some camera feeds, or plugs that make network connections, then anywhere from 12 hours to several days later the -Wave plugin becomes non-responsive as does the HS web server (it will request authentication, but it won't deliver any content) requiring a forced restart.
I've just installed your plugin now and will let you know if it helps 👍
BLGarbage testing for the past week has been a game changer. For around 2.5 days it would start at around 129MB and grow to maybe 169MB before BLGarbage cleaned it back down to 129MB again. This was hourly so I reduced it to 30 minutes to ensure it stayed nice and clean.
Sadly after 2.5 days the memory usage would start growing and BLGarbage didn't seem able to control that - 169MB, 174MB, 182MB, 190MB, 200MB, 216MB, POOF HS4 gone.
So what I now did was have BLGarbage doing the clean every 30 minutes AND I have set HS4 to reboot every night at 4AM. Seems to be a good combination - albiet a sad necessity, under HS3 I could be running for several months until I decided to do Rasbian or HS updates.
Sadly two agos it still happened though - by around 6pm two days ago I saw memory usage was at 210MB and I though ****, I think she's gonna blow. Sure enough next thing I walk down our passage and nothing happened, my wife opens the pantry and nothing happened, yep HS4 has gone bye bye. Had to power cycle.
But yesterday was perfectly fine - I got home quite late in the evening and checked her and she was smack on 129MB.
So two outages in 7 days instead of 7 - one of them avoidable if I had the daily reboot setup at that point.
Still not 100% reliable but a tremendous improvement in compensating for whatever is going wrong in HS4
Comment
-
Originally posted by Tillsy View Post
BLGarbage testing for the past week has been a game changer. For around 2.5 days it would start at around 129MB and grow to maybe 169MB before BLGarbage cleaned it back down to 129MB again. This was hourly so I reduced it to 30 minutes to ensure it stayed nice and clean.
Sadly after 2.5 days the memory usage would start growing and BLGarbage didn't seem able to control that - 169MB, 174MB, 182MB, 190MB, 200MB, 216MB, POOF HS4 gone.
So what I now did was have BLGarbage doing the clean every 30 minutes AND I have set HS4 to reboot every night at 4AM. Seems to be a good combination - albiet a sad necessity, under HS3 I could be running for several months until I decided to do Rasbian or HS updates.
Sadly two agos it still happened though - by around 6pm two days ago I saw memory usage was at 210MB and I though ****, I think she's gonna blow. Sure enough next thing I walk down our passage and nothing happened, my wife opens the pantry and nothing happened, yep HS4 has gone bye bye. Had to power cycle.
But yesterday was perfectly fine - I got home quite late in the evening and checked her and she was smack on 129MB.
So two outages in 7 days instead of 7 - one of them avoidable if I had the daily reboot setup at that point.
Still not 100% reliable but a tremendous improvement in compensating for whatever is going wrong in HS4
~Bill
Comment
Comment