Open a new thread so this situation can be analyzed in detail. This behavior has nothing to do with Blockly. Something is running amok on your machine consuming resources and forcing OH to have to wait.
@florian-h05 i just want to inform you that after the update to OH4.0.2-1, the delay is still there.
To make it sure i restarted OH twice and also uninstalled and installed the JS addon.
as i said already, i can live with that, because i ported all my rules already and i know that it’s just on the first run.
Fully disagree. Try to develop a new rule.
My Wife told me that rules they must be fired before are slow after a while. That happens with 4.0.1. If 4.0.2 didn’t fix it then that will not be satisfied for me.
As discussed above, there are 2 problems. Slow execution which happens the first time a rule is run and what you are seeing. That’s why I asked you to open a separate thread.
I can confirm, that now after 4.0.2-1 upgrade, rules run very slow.
Normal it takes to send a mail and a WhatApp a couple of secounds.
Now it takes 55 sec. (55 sec the rule itself shows the icon “running”)
It’s not important for me if I get the notification that rain started or something else
happend, like power off from a charger, but compared to 3.4.4 it seems a problem.
This only happens on my testsystem with this configuration:
Release = Raspbian GNU/Linux 11 (bullseye)
## Kernel = Linux 6.1.21-v7+
## Platform = Raspberry Pi 3 Model B Plus Rev 1.3
## Uptime = 17 day(s). 14:44:0
## CPU Usage = 2.01% avg over 4 cpu(s) (4 core(s) x 1 socket(s))
## CPU Load = 1m: 2.14, 5m: 2.36, 15m: 1.75
## Memory = Free: 0.00GB (1%), Used: 0.93GB (99%), Total: 0.94GB
## Swap = Free: 2.33GB (78%), Used: 0.66GB (22%), Total: 2.99GB
## Root = Free: 20.09GB (72%), Used: 7.67GB (28%), Total: 28.98GB
## Updates = 0 apt updates available.
## Sessions = 1 session(s)
## Processes = 125 running processes of 32768 maximum processes
Yep… Just try to develop a new rule… That drives me total crazy if you hit run and then you change something small. Oh, forget something and hit again run and wait…
As you can see memory usage is 100% and swap usage is 10%, which indicates that the system does not have enough memory. Using swap instead of memory can heavily affect overall performance.
I think @rlkoshak wrote a more extensive post about this topic, but I cannot find it currently …
Ok, this mean, more or less, that the “old PI3” can not more used for an default installation with 4.02 to get a propper UI performance and a quick tasking from the rules. So a clear recommentation for a PI4!
As with most things it depends. If all you are running is OH 3 with a modest configuration an RPi 3 is probably fine. If you have ZRAM configured and running InfluxDB, Mosquitto, and NodeRed an RPi 3 is probably not enough.
Thanks Rick I only recommend this to the Users which maybe not have it on their
shopping list, that when they upgrade from a OH 3.4x System to an OH 4.0x which was running on an
PI3, that they shall order an PI4, that is running smoove again as was in past …
Order already done for me…
New HW has arreived:
Funny thing ist, that I have a 1:1 copy from my configuration. The production system and a testsystem.
Different is only the on the testsystem all rules a deactivated.
On the production (with the new HW) the rules are slower that on 4.0.2 and the testsystem (with the current used hw for pro) the rules are much, much slower ~ feeling ~3 times.
So for me it seems, that from 3.4.4 to 4.0.3 something has been changed in this way, that ist blocking a fast run from the rules. Also the hint from open,edit,close, and run the rule is NOT making the rule faster.
I’m not talking about a issue in performace between 4.0.3 and 4.0.2
Rich says it’s the old HW (Pi3), so I orderd a new one Pi4 and still have the issue,
that rules that where running in 3.4.4 are now much slower in my prod system, and much much much slower in my testsystem. As told, it’s an 1:1 image copy and only the rules are disabled all on the testsystem.
I disabeld, the „Use Included Library“ in the JavaScript Scripting Binding settings.
Restarted OH, and the speed is the same was ist was. Not real a good performance.
I only recommend this to the Users which maybe not have it on their