I dont have that problem atm, but i’m pretty sure there are no double runs that time because i only have one docker instance.
And by the way i’m also back on 2.23.02 again because as seen in my comparisons it is a pain in the butt to live with that delays.
But lets get to that architecture thing again, could it be possible that just the amd64 port has a bug in it the other versions are not affected by?
I mean @helipus and i are affected in the same way with starting at the same updated version.
We have different hardware since i use a i5 6500 4cores 4 threads with 32 gb ram running the dockers of ssd which should be enough speed to handle deconz (like version 2.23.02 always shows). we Could compare the devices we use… but in first place i think the lowest common denominator should be the architecture the docker runs. As mentioned of Helipus the usage of cpu and i guess of the whole system rises equal to the number of devices. Maybe its just that we are facing that problems because not many people use amd64 with 100+ devices daily or had given up and switched to z2m or something cause there is no way to get new versions running as good as old ones.
In the other thread i was posting the issues got better in the ARM version that were build by manup. the focus there was just on that ARM architecture
Is there a test setup of the devs running amd64 higher than version 2.23.02?