Please note that this is just a guide. The CPU and memory recommendations are estimates. Results may vary depending on the deployment method used (VM, AMI, physical HP Proliant server or NAP server), specific VM controller (if using VM), and how much bandwidth is being run on each stream.
CPU
Assuming each individual stream is not more than 25 Mbps, it is recommended to assign 2 CPU cores as a baseline for the Alta server (to cover the OS, web server and other background services), and another 1.5 CPU cores (rounded down) for each Alta channel (so a minumum of 3 CPU cores if there is a single Alta channel, four if 2 channels, etc). If each stream is above 25 Mbps, this recommendation should be doubled.
RAM / Memory
Also assuming each individual stream is not more than 25 Mbps, it is recommend to assign about 4GB of RAM for the first channel and 1GB of RAM for each additional channel.
Networking
A 1 Gbps interface typically can handle up to 20 transport streams with up to 25 Mbps / stream. More streams (or bandwidth per stream) will require a 10 Gbps interface or multiple 1 Gbps interfaces (Please note that though the VM, AWS AMI, and physical HP Proliant deployment options for Alta can support the 10 Gbps interface, the physical NAP server can only support up to four 1Gbps interfaces and not the 10Gpbs interface.)..
Note: It is not recommended to saturate a 1 Gbps interface above about 500 Mbps in most cases, or you could risk packet loss when there are bursts.
There is no minimum or maximum number of network interfaces that are compatible with Alta – any number will work, as long as it fits on the server. There are 3 distinct network "use types", but these can be combined as desired into the same interface.
- Outbound connection to internet - iCap and licensing
- Local management - stream setup and monitoring
- Media - transport stream data (there could be any number of media interfaces. There can be any number of 'Media' interfaces