3 ms·
> Single camera per instance (e.g. One Docker container per camera). One camera per Docker instance? This is going to eat up hardware resources like Fat Albert.
by bsenftner 5y ago
> Single camera per instance (e.g. One Docker container per camera).
One camera per Docker instance? This is going to eat up hardware resources like Fat Albert.
- daniellarusso 5y agoHow does Fat Albert eat up hardware resources? Also, don’t you need to know the specs of the individual container instances before determining it will be resource starved on the host? I have an off-the-shelf CCTV DVR that supports 4k with up to 8 cameras, but it struggles with more than 4.
- bsenftner 5y agoI write video security software, and the support logic to manage a single camera is quite low. Whereas the supporting infrastructure for this conglomeration is quite large. I know this field of tech intimately, yet when I see projects like this I ask myself "what are they doing with all this infrastructure? why?"
- okamiueru 5y agoWhat kind of hardware resource would this eat up? Maybe on non-linux where docker isn't as efficient? There is next to zero extra memory overhead on Linux, as the static parts are shared. Computational overhead is also linear with work, which would mostly be the case regardless.
- daniellarusso 5y agoThe other cool thing, to me, is you can keep adding cameras and do not have to replace hardware, just add more.
- bsenftner 5y agoIt's not just the use of Docker, the infrastructure they're using is heavier than necessary. Quite a bit.
- mrweasel 5y agoI’ve noticed that software more and more being designed that way. Multi-tenancy is out the window, just run multiple instances. For some applications it’s certainly easier, but as with so many other things it’s overused.