fenderman
Staff member
- Mar 9, 2014
- 36,892
- 21,408
The issue in this thread is directly related to a memory leak and will occur regardless of any settings if you have a bad driver... Limit decoding will cause issues with motion detection...I was looking for something else and found this. In case anyone is interested I'll give my two cents worth.
Blue Iris has become a very sophisticated program. Unfortunately that equates to high CPU and memory resources. But if you don't need all of the bells and whistles turn that feature off and save some resources. If you don't know what it is you probably don't need it. Pick a camera and experiment, and write it down as you go so you can restore it if it doesn't work. After making a change give BI a few minutes to settle down and don't look for immediate results.
The largest CPU savings will come by checking "Limit decoding unless required" in the Video tab of the Camera Properties box. The next big savings will come from getting the time and date from the camera and turning off the overlay in BI. And of course turn down the FPS from the camera to, at the most 12, and some cameras can even stand 10 or 8. This forum has a very good explanation of all of this at: Optimizing Blue Iris's CPU Usage | IP Cam Talk
I have Windows 10 with Intel 7700 and 32 G of ram and have BI running at 10 to 15 % and 1.5 G of ram with seven cameras and a self contained video card on the mother board. It does jump occasionally but I don't see 70 or 90 % and the web server feature seems to work just fine.