Skip to content

Resource requirement

The minimum memory and cpu requirements for each Ixia-c components are captured in the following table. Kubernetes metrics server has been used to collect the resource usage data.

The memory represents the minimum working set of memory required. For protocol and traffic engines, it varies depending on the number of co-located ports. For example, multiple ports are added to a 'group' for LAG use-cases, when a single test container has more than one test NIC connected to the DUT. The figures are in Mi or MB per container and do not include shared or cached memory across multiple containers/pods in a system.

Component 1 Port (Default) 2 Port 4 Port 6 Port 8 Port
Protocol Engine 350 420 440 460 480
Traffic Engine 60 70 90 110 130
Controller 25*
gNMI 15*

Note: Controller and gNMI have a fixed minimum memory requirement and is currently not dependent on number of test ports for the topology.

The cpu resource figures are in millicores.

Protocol Traffic Engine Controller Engine gNMI
Min CPU 200 200 10 10

Minimum and maximum resource usage based on various test configurations

Depending on the nature of the test run, the memory and cpu resource requirements may vary across all Ixia-c components. The following table captures the memory usage for LAG scenarios with varying numbers of member ports. The minimum value represents the initial memory on topology deployment and the maximum value indicates the peak memory usage during the test run. The values are in Mi or MB.

Component Min/Max 1 Port 2 Port 4 Port 6 Port 8 Port
Protocol Engine Max
Min		 348
323		 423
360		 455
360		 464
360		 492
360
Traffic Engine Max
Min		 58
47		 68
49		 90
49		 111
49		 134
49
Controller Max
Min		 21
13		 21
13		 23
13		 24
13		 25
13
gNMI Max
Min		 14
7		 14
7		 14
7		 14
7		 14
7

Following is the memory usage variation with scaling in the control plane. The variation is on the number of BGP sessions (1K, 5K, and 10K), in a back to back setup. The values are in Mi or MB.

Component Min/Max 1K 5K 10K
Protocol Engine Max
Min		 516
323		 906
323		 1367
323
Controller Max
Min		 53
12		 149
12		 259
12
gNMI Max
Min		 7
7		 7
7		 7
7

Following is the memory usage variation with scaling in data plane. The variation is on the number of MPLS flows (10, 1K, and 4K), in a back to back setup with labels provided by the RSVP-TE control plane. The values are in Mi or MB.

Component Min/Max 10 1K 4K
Traffic Engine Max
Min		 58
47		 59
47		 95
47
Controller Max
Min		 18
12		 46
12		 120
12
gNMI Max
Min		 10
7		 17
7		 28
7