Hi Blade,
I've discovered a few problems with the PI, as I have an event currently set to "if HS3.exe is greater than 97% over 10 minutes, restart homeseer".
I kept seeing this trigger more and more, so periodically checked the history of the process - one time it kicked a restart off while viewing the history, yet task manager and the history itself were not above 50% at the time - nominally, if I watch the process, the total CPU is around 30%.
So, the problem is twofold:
one - the CPU reported for HS3.exe is not accurate. Indeed, here's something which is really odd from history:
Two - the triggering part (trigger if above x% for y minutes) is not working either - I've seen the event trigger when total, not HS3.exe usage, CPU spiked for one sample.
I'm thinking the PI is summing up all the child processes somehow incorrectly, so is triggering all the time.
PI version is 2.0.10.0
I've discovered a few problems with the PI, as I have an event currently set to "if HS3.exe is greater than 97% over 10 minutes, restart homeseer".
I kept seeing this trigger more and more, so periodically checked the history of the process - one time it kicked a restart off while viewing the history, yet task manager and the history itself were not above 50% at the time - nominally, if I watch the process, the total CPU is around 30%.
So, the problem is twofold:
one - the CPU reported for HS3.exe is not accurate. Indeed, here's something which is really odd from history:
24/10/2019 08:58:55 | 119.82% |
I'm thinking the PI is summing up all the child processes somehow incorrectly, so is triggering all the time.
PI version is 2.0.10.0
Comment