That's what I did till I read this note: Knnniggett noted here that if an FFMPEG camera goes down (offline) and there is no MaxFPS in ZM, then ZM eats up CPU trying to reach it. I verified this to be true - I took one of my ffmpeg cameras offline and the CPU shot up to 67% (from 18%). I took two off, and it went to 86% constant.
To avoid this problem, I followed the advice provided in the thread I linked to above - I set in-camera FPS to "x" and ZM maxFPS to x+3 (some number more than x, large enough to make sure rounding off errors don't make ZM rate-limit a live camera). I validated this approach by again taking two of my cameras offline, and the load increase was minimal.
knnniggett wrote:Couple of follow up notes:
- For ip cameras, always set the frame rate in the camera, *not* in zoneminder. Trying to reduce the frame rate by putting values into the monitor max fps & alarm max fields is guaranteed not to work correctly.
- Yes, the WiKi is editable by anyone. Please help out by keeping it up to date.