Good question, I did lots of profiling and tests the recent days and there are multiple issues shown in the result which can impact CPU usage, and some of these have been around for a long time. While the first internal testing versions fixed a couple of these it didn’t fix the problems for in the developers setup.
Yesterday I found one one regression which does fit in above mentioned time frame and is quite drastic, a timer could be firing constantly trying to process the outgoing commands queue (even if empty), this regression could be pointed to a change from 2023-09-28. In my local tests the profiler shows a much healthier picture now but that needs to be confirmed with other setups.
I’ve created two test versions for ARM and ARM64 if you like to give it a go.
deconz_2.25.1_72175c-debian_armhf.deb
deconz_2.25.1_72175c-debian_arm64.deb
This can be installed via sudo dpkg -i <filename.deb>
After initial build up of the node graph with lines the CPU usage should drop down to 2–5 %