Dzvents consumes high CPU

[waltervl]

As a test you can just add the Domoticz logging demo script. It should do nothing until you switch the dummy test device. I wonder if that also consumes that high amount of CPU resources.

[janpep]

One thing I noticed is after enabling this script Domoticz starts consuming an extra ~5-7% CPU usage.

I think that EventSystemQueue processes all events, including those defined in Blockly.
I don't quite understand what the problem is. That the CPU doing something? And if the CPU does this four times a day, what is the problem?
In my case, it ranges from 1 to 10, but mostly between 2 and 5 and so varies greatly depending on what's running. Not surprising. I have several scripts with quite a few calculations.

It seems that this script should only run 4 times a day..

If RIVM only updates the data four times a day, it does not seem very useful to run it more often. It always returns the next four time points.
My Dutch local 'Stookwijzer' script always calculates using the current and expected values and gives more time points.

[waltervl]

I splitted off the CPU issue from the RIVM topic as it is not related. I have the same Domoticz version and Ubuntu, not having this issue....

I am also not seeing this on latest beta.
Do you have a lot of devices?

[janpep]

I splitted off the CPU issue from the RIVM topic as it is not related. I have the same Domoticz version and Ubuntu, not having this issue....

Yes, thank you very much. I already had the feeling it was getting a bit off topic.

[gizmocuz]

@gbonny, they is quite a few. And if you have scripts that could react on any device update, you will CPU usage
Upgrade to the beta and you should see already less CPU usage

[gizmocuz]

@gbonny, yes once all changes in the beta are stable (they are quite stable but there is a big frontend patch that possibly needs more attention)