Page 2 of 2
Re: 2 minutes delay in device trigger DZVents in log
Posted: Sunday 30 December 2018 15:19
by klaaspiet
Hey. Thank al for the help. I dit der that the rate limit of the p1 USB hardware is 0. If i increase that the CPU is going down.
Re: 2 minutes delay in device trigger DZVents in log
Posted: Sunday 30 December 2018 16:10
by waaren
klaaspiet wrote: ↑Sunday 30 December 2018 15:19
the rate limit of the p1 USB hardware is 0. If i increase that the CPU is going down.
The value of 0 is the default. The CPU usage will go down if you raise it but I expect that this is not the root cause of your CPU usage problem.
Re: 2 minutes delay in device trigger DZVents in log
Posted: Sunday 30 December 2018 16:47
by klaaspiet
I set the rate limit on 120sec. And now my CPU is 21 25%. And my scrips are working fine.
Re: 2 minutes delay in device trigger DZVents in log
Posted: Sunday 30 December 2018 16:59
by Egregius
Even 20% is way to high. My cpu usage is 0,2 to 0,5% with zwave, rfxcom, xiaomi, 150 used devices, 400 variables and lots of scripts.
Re: 2 minutes delay in device trigger DZVents in log
Posted: Sunday 30 December 2018 17:51
by waaren
Egregius wrote: ↑Sunday 30 December 2018 16:59
Even 20% is way to high. My cpu usage is 0,2 to 0,5% with zwave, rfxcom, xiaomi, 150 used devices, 400 variables and lots of scripts.
Wow these Raspberries must be much faster in Belgium than they sell them in the Netherlands...
Re: 2 minutes delay in device trigger DZVents in log
Posted: Sunday 30 December 2018 18:26
by klaaspiet
waaren wrote: ↑Sunday 30 December 2018 17:51
Egregius wrote: ↑Sunday 30 December 2018 16:59
Even 20% is way to high. My cpu usage is 0,2 to 0,5% with zwave, rfxcom, xiaomi, 150 used devices, 400 variables and lots of scripts.
Wow these Raspberries must be much faster in Belgium than they sell them in the Netherlands...