DSL scripts composed in OH3 main UI editor run slow, out of memory errors, high CPU

Pedals2Paddles · December 25, 2020, 1:31am

Has anyone else written scripts or rules in the OH3 Main UI DSL editor? If so, have you found that these rules perform very poorly, taking longer than they should to execute? Have you found it resulting in java heap space errors, running out of memory, and CPU usage getting pegged? I and one other member here have experienced this. Even on multiple fresh clean installs.

I have written the same rule doing the same thing in the ECMA script editor in the OH3 main UI and it performs perfectly. This only seems to happen with DSL scripts and it only seems to be with DSL scripts written in the Main UI editor. In other words, not text file rules.

Fishing for anyone else with this issue to forward to developers for troubleshooting.

hafniumzinc · December 25, 2020, 6:50am

Could you post the DSL and ECMA versions of each script to compare?

Boby · December 28, 2020, 9:42pm

Today I migrated my old .rules files into the GUI. Since I don’t “speak” ECMA, I went for DSL rules.
Two hours ago I had my first “Java heap space” exception and the system became unresponsive.
I also noticed that sometimes very simple DSL rules take 7-10 seconds in execution,

So, yes, there is definitely an issue with DSL rules defined on the GUI (at least) in OH3.

Boby · December 28, 2020, 9:48pm

This issue is not really new:

github.com/openhab/openhab-core

[OH3] Defining Rules in Main UI increases CPU Load

opened 06:36PM - 30 Nov 20 UTC

closed 12:18PM - 03 Jan 21 UTC

gdolfen

I have a problem with high cpu usage in M2 and M3. I figuerd out that the reaso…n are rules which are configure over main ui. I started with 4 rules in a *.rules file with a cpu usage of 1%. In main ui they always stay on "IDLE" after migration them to main ui by copy the generated code by the code view everything was fine, but the logs was full with ERRORs "No pre-parsed script found for e3dc-2". So I deleted the line "// context: e3dc-2" from the code and the log disappears, but the cpu was increased up to 5% per rule and the state stays always on "RUNNING". Here is my rule code: ``` triggers: - id: "0" configuration: itemName: E3DC_Extern type: core.ItemStateChangeTrigger conditions: [] actions: - inputs: {} id: script configuration: type: application/vnd.openhab.dsl.rule script: | // context: e3dc-2 var Number negativeValue = E3DC_Extern.state as Number var Number positiveValue = negativeValue * -1 E3DC_String3.postUpdate(positiveValue) type: script.ScriptAction ``` It seemed that the rule is parsed every time, because every 5 seconds (5 seconds update period of item E3DC_Extern) I got the log error. Maybe preparsing the rule after saving it in main ui makes the trick.

Pezzi42 · January 14, 2021, 3:12pm

Have the same problem (out of memory, OH3 takes 20% of available memory).
Not sure whether it actually does relate to a rule, but the OOM error definitely appears at a time when a rule was running…

Boby · January 14, 2021, 3:32pm

What version are you running?
Should be fixed on the 3.1 snapshot already

Pezzi42 · January 14, 2021, 3:43pm

Running 3.0.0-1 - how far along is 3.1? I use the stable repository…

Boby · January 16, 2021, 2:28pm

I’m currently on 3.1.0-SNAPSHOT - Build #2143 and I can only recommend everybody to switch to the snapshot. It’s stabe, you get daily fixes - and a lot of the problems in 3.0 have been fixed already.

Pedals2Paddles · January 17, 2021, 10:49pm

Fantastic! Glad this got addressed so quickly. Is there anything in 3.0.1 you’re aware of that is worse or a new issue not in 3.0.0? I’ve looked for snapshot release notes but not finding anything.