Blue Iris

I've noticed a strange issue after upgrading to the latest version of CPAI. After around 24 hours of use, my GPU idles at roughly 30%, which is highly unusual. Normally, when I open the Blue Iris interface, the GPU usage increases temporarily, and minimising the interface brings the idle usage back down to around 0–1%. However, this behaviour has changed, and the GPU now stays locked at 30% even when idle.

While this doesn't seem to affect system performance directly at the moment, it is a concern. Having 30% of GPU resources utilised for seemingly nothing could impact inference performance, as that headroom is already allocated.

I'm sharing this here as it clearly isn't normal behaviour, and others might be experiencing the same. My suspicion is that this is an issue on the CPAI side rather than with Blue Iris itself, though I'm not ruling anything out. I'll likely raise this with the CPAI team directly.

In the meantime, the only workaround is to reboot the system, but I can't be rebooting daily - just not practical.

If anyone has experienced something similar or has suggestions, I'd love to hear them.

Cheers,
SN

What version of BI are you actually using, have your tried rolling back to a prior version to confirm the issue is BI version specific, has there been any driver updates or Windows updates applied recently.

Have you looked at the CPAI console and log? Maybe you can see what it is doing.
I watched CPAI and saw that it examines models that BI is supposedly not calling (I excluded them in BI). I don't know why. The only way to stop that was to remove the models from the custom models folder.
Maybe your CPAI installation activated multiple engines?

BruceH wrote: ↑Sun Dec 15, 2024 12:34 pm What version of BI are you actually using, have your tried rolling back to a prior version to confirm the issue is BI version specific, has there been any driver updates or Windows updates applied recently.

I should’ve mentioned the versions earlier. I’m on the latest BI (5.9.9.14) and CPAP (2.9.5). My Windows did indeed update , couple days ago from 23H2 to 24H2, and I think the 24H2 update might be the issue. I did roll back to a previous version to check, but it was the same... I should’ve mentioned that too. Tried all the obvious stuff as well.

System restore to back to 23h2 me thinks!

PaulDaisy wrote: ↑Sun Dec 15, 2024 4:49 pm Have you looked at the CPAI console and log? Maybe you can see what it is doing.
I watched CPAI and saw that it examines models that BI is supposedly not calling (I excluded them in BI). I don't know why. The only way to stop that was to remove the models from the custom models folder.
Maybe your CPAI installation activated multiple engines?

I’ve checked CPAI, and everything’s above board—only YOLO5.NET is running. For context, 24H2 was installed recently, and everything was fine prior to that, apart from the recent BI updates.

At this stage, all signs seem to point to 24H2. I’m rolling back to test again.

Thanks for the input!