Slightly off on a tangent but I tried disabling motion detection earlier in the Rekor agent, it then assumes a vehicle is passing through the scene constantly. I will experiment to see if this reduces spikes at all on the CPU. Because my CPU is a bit on the old side I get a good idea of any benefits, doesn't take much to spike it to high 90% region during multiple camera events. Will soon know, I would rather have constant CPU usage at 40-50% without huge spikes which then overload it.
Initial testing actually looks promising, I would say an improvement in CPU usage over having motion detection enabled, less spiking and only slightly more continuous CPU usage by Rekor. I would assume this also means less chance of missing a plate if the motion detection failed in Rekor, possibly at night if you were running very high shutter, I have seen this before. I will continue testing today and see how it works out.
It would appear that my Deepstack is also working better with this setting, presumably leaving a bit more wiggle room within the CPU, one of my cameras would likely miss 50% of Ai events due to location/scene, it is closer to 100% with Rekor motion disabled. This setting is probably irrelevant for people with more powerful or newer processors, with my old i5 4th gen and 11 cameras, not so much