viinex can run on Linux (x64 and arm64 hardware) and on Windows (x64 only). Scenarios with deployment into bare host OS, as well as into containers (Docker, LXC) or virtual machines (KVM, Hyper-V, VMWare) are all supported. There’s basically no performance penalty in any of these scenarios.


On a low-performance power-saving Intel CPU (like U-series Core i3, dual core, working at the frequency of 2GHz), viinex utilizes about 2% of time at one core per one video channel being recorded. It also takes additional 1% of time on one CPU core to re-stream one video channel to a remote client, no matter whether it is a live stream or a video archive data. That is, with viinex one can write and re-stream video data from at least 50 video cameras using this moderate CPU. With a quad-core i5 CPU this number is doubled.


For arm64, results given for a rk3399-based system. Viinex utilizes 4% CPU time per each video channel being received and written, and additional 2% of CPU time per each video channel being re-streamed to a remote client. These numbers refer to the whole device (not to a single core). Overall the system is capable of serving (writing and re-streaming) about 12 video cameras with viinex software.