Hаrdwаre and systеm requirements
The successful installation and operation of Mediaserver, along with the assurance of system stability and efficiency, depend upon the thorough preparation of equipment and a comprehensive review of system requirements.
Important: The calculations provided in this documentation section are for general guidance only.
For precise equipment recommendations and hardware sizing, particularly for complex, multiserver setup, we strongly recommend consulting our technical support team.
Hardware requirements
To accurately calculate the necessary hardware resources, consider the following key parameters:
Total bitrate of cameras.
Archive storage time.
Used codecs.
A number of streams from one source and stream parameters.
A number of users.
In addition to the previously mentioned parameters, it's crucial to consider the future load on the server. The server load depends on the following settings:
A number of incoming streams.
Parameters of incoming streams.
A number of sources that Mediaserver will interact with.
Archive recording.
An archive size and retention period.
A number of users.
Important: The calculations provided in the table below are approximate and show the estimated system performance under the following hardware characteristics:
Servers with Intel Xeon Gold 6226R processors operating in powersafe mode at a frequency of 1.59 GHz were used.
IOPS values were taken for an Avago 3108 RAID controller with a maximum stream bitrate of 3.26 Gbps.
Actual performance may vary depending on the configuration and model of the equipment used.
Number of streams with archive | CPU load | RAM | IOPS | Network |
|---|---|---|---|---|
100* | <1 vCPU | ~4 GB | ~220 | ~325 Mbit/s |
500* | <2 vCPU | ~20 GB | ~1115 | ~1,6 Gbit/s |
1000* | <4 vCPU | ~40 GB | ~2230 | ~2 Gbit/s |
*Stream bitrate is from 2 to 4 Mbit/s.
Approximate hardware and system requirements
Important: In the table below, the storage volume requirements for HDDs are provided as a reference for 2 Mbit/s video streams, assuming continuous 24/7 recording during a 30-day period.
The actual storage needed can vary significantly based on several factors. The actual storage volume is calculated individually for each installation and can vary significantly based on several factors:
Resolution of cameras
Codecs used
The level of compression
Activity in the scene being recorded
A specific recording mode employed
Archive retention time
Mediaserver | ||||||
Number of streams* | 200 | 500 | 1000 | 2000 | 5000 | Platform |
Processor | 4 vCPU | 8 vCPU | 12 vCPU | 16 vCPU | 32 vCPU | Ubuntu 20.04 Rack/VMware (or equivalent) |
RAM | 16 GB | 48 GB | 64 GB | 80 GB | 160 GB | |
SDD | 128 GB | 128 GB | 128 GB | 128 GB | 128 GB | |
Network adapter | 1 Gbit/s | 2х1 Gbit/s | 10 Gbit/s | 10 Gbit/s | 2х10 Gbit/s | |
Required HDD volume (archive, 30 days) | 60 TB | 300 TB | 600 TB | 1200 TB | 3000 TB | |
*The ratio of HD to SD streams is 2 Mbit/s to 0.2 Mbit/s, which equals 1 to 1.
A configuration for 1000 channels can handle up to 2 Gbit/s of incoming camera traffic.