I don't know, try disabling 3/4 of the cameras and see if you can get it to run with 5-10 cameras. Since it's an 8th generation Intel chip you should read the thread that has info on the Intel memory leak.
URGENT: Blue Iris Troubleshooting
- Thread starter Amu
- Start date
Let's see what the CPU is with 2 cameras enabled.
Teamviewer won't work until you get the CPU under control.
Teamviewer won't work until you get the CPU under control.
Sounds better. Now just add a camera at a time and watch the CPU. Should be able to finish it from here.
DO you have a link for the same? I think ive practically almost read everything on this troubleshooting section of Blue Iris now!
We are still not able to do a web login or log in from the application though apart from the CPU usage being 10%
We are observing the CPU usage going upto 100% on web login and dropping as soon as logged out.. any thoughts?
As @smiticans said above, here's direct link, follow exactly : The Quick Sync Video Memory Leak: 8th Generation (Coffee Lake)
I know this is late, but here is my analysis of the situation.
(((2 * 6) + (2 * 4) + (29 * 3)) * 15) = 1605
1605 is your megapixels per second (MP/s) with all cameras set to 15 FPS. It is really close to the limit of what an i7-8700K will handle, but it SHOULD be able to handle it if everything is configured properly as described in Optimizing Blue Iris's CPU Usage | IP Cam Talk but it will probably be over 50% load and CPUs like the i7-8700K with hyperthreading go from 50% to 100% pretty quickly.
This means you have turned on the "Limit decoding unless required" feature on most or all of the cameras, and that is the only reason your CPU usage is manageable. If you had been doing this two or three months ago I would have told you that you can't do this and still use the web server, because that "limit decoding" setting gets temporarily disabled for every camera being viewed through the web server and the first thing the web UI does is load the All cameras group. You've seen the result of that.
Fortunately there is a fairly new option to let you run with it, located here:
"Require/decode all camera frames when streaming". Turn that off. Anyone relying on "limit decoding" to keep CPU usage under control should turn off the setting above for all their large camera groups.
(((2 * 6) + (2 * 4) + (29 * 3)) * 15) = 1605
1605 is your megapixels per second (MP/s) with all cameras set to 15 FPS. It is really close to the limit of what an i7-8700K will handle, but it SHOULD be able to handle it if everything is configured properly as described in Optimizing Blue Iris's CPU Usage | IP Cam Talk but it will probably be over 50% load and CPUs like the i7-8700K with hyperthreading go from 50% to 100% pretty quickly.
This means you have turned on the "Limit decoding unless required" feature on most or all of the cameras, and that is the only reason your CPU usage is manageable. If you had been doing this two or three months ago I would have told you that you can't do this and still use the web server, because that "limit decoding" setting gets temporarily disabled for every camera being viewed through the web server and the first thing the web UI does is load the All cameras group. You've seen the result of that.
Fortunately there is a fairly new option to let you run with it, located here:
"Require/decode all camera frames when streaming". Turn that off. Anyone relying on "limit decoding" to keep CPU usage under control should turn off the setting above for all their large camera groups.
Last edited:
