With that setup, I probably could have thrown 20+ cameras at it as there's not much actual work for the computer to do other than recording the streams.īack when I put my system together, I didn't really have any idea of what to buy, so I just built a Mini ITX box based around a lower power i7. I have all 5 of my cameras using motion detection based on certain zones I've set up, and that's the majority of the CPU usage.Īt one point when I was trying out a different VMS, I didn't have time to set up the motion detection, so I just set it to record constantly. Motion detection does come with a CPU hit, it's obviously more and more of a hit the more pixels you throw at it. For those, most of the software I've used does allow hardware encoding (Quick Sync, NVENC, VCE), but unless you're close to maxing out the CPU already, then it's not necessary. But, if you have any that are older and don't support h264, then you'll want to set the VMS to transcode them to h264. With those, you just set the VMS software to directly record the video feed unaltered. The vast majority of modern cameras output h264 video. Once I moved it over to my actual i7-4770S, it sits at about 20%, so I have a lot of headroom for adding more cameras. On my little i3 test rig, that setup was averaging about 40% CPU usage with motion detection running on all cameras. Resolution is the biggest impact on CPU usage. There's a lot that goes into it, and 9 is a lot, but it doesn't require any sort of super computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |