I had an interesting problem over the last 2 weeks. BI was consuming 90+ CPU any time I was viewing in Chrome, and playback was poor. Scrubbing resulted in 100% CPU and timeouts.
I RDPed into the box, and was reporting similar usage, whether or not the BI console was running. So I disabled every single camera from the console, and the BI process was still consuming 60%, even with the BI window not running and no viewers logged in.
Stopping the BI service reduced the CPU usage, of course, and restarting the BI service resumed the 90% CPU usage.
I tried repairing the database and even deleting and rebuilding the database, and nothing seemed to fix the problem.
So I went to my V: drive, where I store all my footage, and deleted the whole BI directory, rebooted, and deleted/rebuilt the BI DB. CPU usage is now back to its normal << 30% at idle (e.g. pulling from 26 cameras, but no BI window or viewer).
Any idea why a corrupt file would do this, and if there's a way to fix without deleting all my footage? So many missed coyotes . . . .
I RDPed into the box, and was reporting similar usage, whether or not the BI console was running. So I disabled every single camera from the console, and the BI process was still consuming 60%, even with the BI window not running and no viewers logged in.
Stopping the BI service reduced the CPU usage, of course, and restarting the BI service resumed the 90% CPU usage.
I tried repairing the database and even deleting and rebuilding the database, and nothing seemed to fix the problem.
So I went to my V: drive, where I store all my footage, and deleted the whole BI directory, rebooted, and deleted/rebuilt the BI DB. CPU usage is now back to its normal << 30% at idle (e.g. pulling from 26 cameras, but no BI window or viewer).
Any idea why a corrupt file would do this, and if there's a way to fix without deleting all my footage? So many missed coyotes . . . .
