Articles in this section

Alta TS Scaling Guide

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), the specific virtual machine (VM) controller (if using a VM), and how much bandwidth is being run on each stream.

 

CPU

For each individual stream of 25 Mbps or less, we recommend two CPU cores as a baseline for the Alta server to cover the OS, web server, and other background services. From there, we recommend another 1.5 CPU cores (rounding up) for each Alta channel. This results in a minimum of four CPU cores if you have a single Alta channel, five if you have two channels, etc.

If each stream is above 25 Mbps, double this recommendation. 

Number of Channels

Base Cores (Operating system,etc):

2, standard

Additional cores per channel:

1.5, rounding up

Total recommended cores
1224
2235
3257
4268
52810
Recommended number of CPU cores for streams of 25 Mbps or less

RAM / Memory

Assuming each individual stream is not more than 25 Mbps, it is recommended to assign about 4 GB of RAM for the first channel and 1 GB of RAM for each additional channel.

Networking

A 1 Gbps interface typically can handle up to 20 transport streams with up to 25 Mbps per stream. More streams (or bandwidth per stream) require a 10 Gbps interface or multiple 1 Gbps interfaces. 

Note: 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 three distinct network "use types", but these can be combined as desired into the same interface.

  1. Outbound connection to internet - iCap and licensing
  2. Local management - stream setup and monitoring
  3. Media - transport stream data: there can be any number of 'Media' interfaces