Openhab 2.2 Odroid c2 - rules running very slow after a few hours

[psyciknz]

I have oh running on an odroid c2…it was running fine till after a few hours when rule processing seems to slow right down.

21:45:00.004 [INFO ] [me.model.script.MorningCentralHeating] - Command Called
21:45:00.002 [INFO ] [rthome.model.script.DayCentralHeating] - Command Called
21:50:59.456 [INFO ] [rthome.model.script.DayCentralHeating] - Checking end time against current.  End: 22 and current 21:50:59.456
21:52:29.500 [INFO ] [rthome.model.script.DayCentralHeating] - (0)   Calculated average: 19.6
21:53:59.522 [INFO ] [rthome.model.script.DayCentralHeating] - (0) Getting average group
21:49:29.375 [INFO ] [me.model.script.MorningCentralHeating] - Checking start/end time against current.  Start: 5 End: 8 and current 21:49:29.374
21:56:59.576 [INFO ] [me.model.script.MorningCentralHeating] - (0)  Getting average from manually calulated average as default
21:58:29.604 [INFO ] [me.model.script.MorningCentralHeating] - (0)   Calculated average: 19.6
21:59:59.626 [INFO ] [me.model.script.MorningCentralHeating] - (0) Getting average group
22:01:29.648 [INFO ] [me.model.script.MorningCentralHeating] - (0)   Calculated average from group: 19.6
21:48:32.179 [INFO ] [.smarthome.model.script.CarportLights] - Command Called
21:47:59.348 [WARN ] [core.internal.events.OSGiEventManager] - Dispatching event to subscriber 'org.eclipse.smarthome.io.monitor.internal.EventLogger@7e7a7ef7' takes more than 5000ms.
21:47:40.597 [INFO ] [me.model.script.MorningCentralHeating] - Command Called
21:47:40.594 [INFO ] [rthome.model.script.DayCentralHeating] - Command Called
22:08:59.777 [INFO ] [rthome.model.script.DayCentralHeating] - Checking end time against current.  End: 22 and current 22:08:59.777
21:47:39.774 [INFO ] [me.model.script.br_master_temperature] - Posting update as difference < 3:  Sensor: 20.1000003815 Stored: 20.1000003815 Difference: 0.0
22:11:59.908 [INFO ] [marthome.model.script.SMSGateway Date] - Command Called
22:13:29.931 [INFO ] [marthome.model.script.SMSGateway Date] - Getting time from raw sms gateway state
22:14:59.956 [INFO ] [marthome.model.script.SMSGateway Date] - Raw time is 1526206492187
21:46:35.573 [INFO ] [marthome.model.script.SMSGateway Date] - Command Called

you can see the times flicking around on these rules where they should be instant. Its after running for about 5 hours.

Java is openjdk since zulu doesn’t see to easily support 64 bit ubuntu on arm.

[Udo_Hartmann]

@psyciknz

Java is openjdk since zulu doesn’t see to easily support 64 bit ubuntu on arm.

Afaik you shouldn’t use 64bit java at arm anyway.
https://docs.openhab.org/installation/index.html#prerequisites

[psyciknz]

oh that works for me, how do I force install of 32bit then? If I follow the zulu instructions it complains that it can’t find a 64 bit version.

HowTo: Install Zulu Embedded Java on Raspberry Pi 3

[Topic updated on 10/Nov/2018 to notify users to use a manual installation method (no repos)] Please see the following link for installation information of Azul Zulu Embedded: [caution_out_of_order_hazard_sign_grande] Don’t use the info below anymore ! [Topic updated on 02/May/2017 to include Zulu Linux APT Repositories] Introduction To run openHAB 2 (OH2) on a Raspberry Pi 3 (rPi3) with the standard Raspbian image, you need a working Java Runtime Environment installed on your system. …

[Udo_Hartmann]

Maybe this will help:

Rfxcom on odroid c2 (arm 64)

I found something on http://docs.openhab.org/installation/index.html: Make sure to use the 32-bit version of the JVM for ARM platforms, even on 64-bit operating systems. Serial connections won’t work with a 64-bit JVM, preventing bindings like Z-Wave from functioning. The problem is that openhab is not fully working on 64bit java on arm. So the solution is to install the 32bit arm jre which can be found at oracle. To make the 32bit binaries work some additional commands are needed: sudo dp…

[psyciknz]

So I got it working on zulu, took a bit.

Had it running over night and it’s performance was better. Didn’t pay attention to my heating control which is supposed to be based on change of temps and between a time period…but when I manually kicked it on, its seemed to come to life.

There seems to be a bunch of processor modes on these boards, and it looked like it was interactive…maybe that scales up and down the cpu. I need to find a more always on option.