Hard to say what is wrong. What if you use the Jpeg HD mode? Do you get a decent video for single cameras that way?
Is it a single processor in the server? Dual processors tend to report 50% when the load is entirely running on one maxed-out processor and can't spread out across two.
JPEG HD is not giving the OCOD, but I'm only getting an updated image every 3-5 seconds.
It's a dual processor system under Proxmox, but I've dedicated 10 CPUs to BI. The cameras are set to stream at 2 FPS h.264.
The other thing I've noticed is that if BI has been running for a day or so, doing a 'net stop
blueiris' takes 3-5 minutes to complete, where it used to take 3-5 seconds. If I do it immediately after startup, it still only takes 3-5 seconds.
This has been sitting here for a day or two unposted while I play with different settings and try and figure stuff out.
I downgraded to 5.5.6.11 which didn't help.
I dug out an old laptop with an I5 8th gen with a 100mbit network interface that I hadn't turned on in a couple months, and that seemed to be working just fine. Then after a couple minutes the Chrome update notifcation came up so I updated, then I started getting the OCOD.
I started playing around with the different quality rates on UI3. From 144 to 480 it seemed to work fine, which seem to be using the sub stream, but started having problems at 720P which seem to switch to the main stream. Which would kind of seem to make sense...The sub stream would be sending less data so it would be less stress on the systems involved....But the systems aren't resource taxed and are more than capable of handling the data volume. hmmm...
With the Reolink cameras, the minimum FPS for the substream is 4, and 2 for mainstream. Which is what I had them all set to.
Watching the FPS on the UI3, when using the 144-480 resolutions, the FPS never went to 0, but it did on the higher resolutions...Why? So I kicked the mainstream up to 4 FPS. The number of OCODs dropped.
So I kicked the substream to 7 and the mainstream to 6 and the OCODs went away!
OK!
So who wouldda thought throwing MORE data at the problem would make it go away?
So....What's going on here? Is Chrome or UI3 being a little too aggressive at detecting frame loss, prematurely closing the connection and restarting? I've tried Firefox, Chrome, and Edge, and they all exhibit the same behavior.