System started trigger in OH3 - lazy execution of first rule execution

[rossko57]

@mark_leonard_tuil

the first time a rule runs this rule takes (a lot) more time than normal.

So far as I know that is still true.

@mark_leonard_tuil

A solution under OH2 was to include a system started trigger in each .rules file like this:

By OH2.4 at least, it got more complicated. The appearance was that infrequently used rules could get garbage collected. Say overnight, then first run next morning would require recompiling and cause delay.
The suggested workaround is a little rule in each xxx.rules file that runs periodically as a kind of “keep alive”.
You might want to see if that has any effect in OH3 with DSL files.

Idea: hack to avoid rule delay, keep time-critical rules in memory

Maybe the java experts can comment on this… Problem: Rules can take 10-20 seconds to trigger if they not have triggered very recently. My theory is that a JIT compiler runs over them before they are executed, and after some time of not using it, the result is purged from memory. Thus it has to be compiled again, which takes time on my Raspi (3+). My solution: I put this in the rule file that I want to prevent from being recompiled: rule "keep this thing in memory" //use the compiled code in t…

I think there are going to be varied experiences in this area, depending on host capabilities.