From 2751906f52d5cb5f592fa01b47b7a2809ef98f54 Mon Sep 17 00:00:00 2001 From: anjan-keysight <84822148+anjan-keysight@users.noreply.github.com> Date: Wed, 6 Sep 2023 05:28:08 +0530 Subject: [PATCH 1/5] Update README.md Data added for minimum resource requirements. --- README.md | 88 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 88 insertions(+) diff --git a/README.md b/README.md index a04a134..c9616b3 100644 --- a/README.md +++ b/README.md @@ -95,6 +95,94 @@ status: state: DEPLOYED ``` +## Minimum 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 resource usage data. The memory represents the minimum working set memory required, and for protocol and traffic engines, varies depending on the number of colocated ports. The figures are in Mi or MB. + + | --------------- | ------- | ------- | ------- | ------- | ------- | + | Component | 1 Port | 2 Port | 4 Port | 6 Port | 8 Port | + | | Default | | | | | + | --------------- | ------- | ------- | ------- | ------- | ------- | + | Protocol Engine | 350 | 420 | 440 | 460 | 480 | + | --------------- | ------- | ------- | ------- | ------- | ------- | + | Traffic Engine | 60 | 70 | 90 | 110 | 130 | + | --------------- | ------- | ------- | ------- | ------- | ------- | + | Controller | 25 | | | | | + | --------------- | ------- | ------- | ------- | ------- | ------- | + | gNMI | 15 | | | | | + | --------------- | ------- | ------- | ------- | ------- | ------- | + +The cpu resource figures are in millicores. + + | ---------- | -------- | ------- | ---------- | ----- | + | | Protocol | Traffic | Controller | gNMI | + | | Engine | Engine | | | + | ---------- | -------- | ------- | ---------- | ----- | + | Min CPU | 200 | 200 | 10 | 10 | + | ---------- | -------- | ------- | ---------- | ----- | + +The operator sets the minimum memory requirement for each ixia-c component depending on the port configuration. The minimum cpu requirement is set to a default value for each component. + +### Minimum resource usage based on various test configurations + +Depending on the nature of test run, the memory and cpu resource requirements may vary across all ixia-c components. The following tables capture the memory usage for lag scenarios with varying numbers of member ports. The minimum value represents initial memory on topology deployment and maximum value indicates the peak memory usage during the test run. Figures are in Mi or MB. + + | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | + | Component | Min/Max | 1 Port | 2 Port | 4 Port | 6 Port | 8 Port | + | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | + | | Max | 348 | 423 | 455 | 464 | 492 | + | Protocol | ------- | ------ | ------ | ------ | ------ | ------ | + | Engine | Min | 323 | 360 | 360 | 360 | 360 | + | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | + | | Max | 58 | 68 | 90 | 111 | 134 | + | Traffic | ------- | ------ | ------ | ------ | ------ | ------ | + | Engine | Min | 47 | 49 | 49 | 49 | 49 | + | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | + | | Max | 21 | 21 | 23 | 24 | 25 | + | Controller | ------- | ------ | ------ | ------ | ------ | ------ | + | | Min | 13 | 13 | 13 | 13 | 13 | + | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | + | | Max | 14 | 14 | 14 | 14 | 14 | + | gNMI | ------- | ------ | ------ | ------ | ------ | ------ | + | | Min | 7 | 7 | 7 | 7 | 7 | + | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | + +Following is the memory usage variation with scaling in control plane. The variation is on the number of BGP sessions (1K, 5K and 10K), in a back to back setup. Figures are in Mi or MB. + + | ---------- | ------- | ------ | ------ | ------ | + | Component | Min/Max | 1K | 5K | 10K | + | ---------- | ------- | ------ | ------ | ------ | + | | Max | 516 | 906 | 1367 | + | Protocol | ------- | ------ | ------ | ------ | + | Engine | Min | 323 | 323 | 323 | + | ---------- | ------- | ------ | ------ | ------ | + | | Max | 53 | 149 | 259 | + | Controller | ------- | ------ | ------ | ------ | + | | Min | 12 | 12 | 12 | + | ---------- | ------- | ------ | ------ | ------ | + | | Max | 7 | 7 | 7 | + | gNMI | ------- | ------ | ------ | ------ | + | | Min | 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 RSVP-TE control plane. Figures are in Mi or MB. + + | ---------- | ------- | ------ | ------ | ------ | + | Component | Min/Max | 10 | 1K | 4K | + | ---------- | ------- | ------ | ------ | ------ | + | | Max | 58 | 59 | 95 | + | Traffic | ------- | ------ | ------ | ------ | + | Engine | Min | 47 | 47 | 47 | + | ---------- | ------- | ------ | ------ | ------ | + | | Max | 18 | 46 | 120 | + | Controller | ------- | ------ | ------ | ------ | + | | Min | 12 | 12 | 12 | + | ---------- | ------- | ------ | ------ | ------ | + | | Max | 10 | 17 | 28 | + | gNMI | ------- | ------ | ------ | ------ | + | | Min | 7 | 7 | 7 | + | ---------- | ------- | ------ | ------ | ------ | + ## Deployment Please make sure that the setup meets [Deployment Prerequisites](#deployment-prerequisites). From 1bb09fb8c1fef2913d9fbb761beeca92e38e803d Mon Sep 17 00:00:00 2001 From: anjan-keysight <84822148+anjan-keysight@users.noreply.github.com> Date: Wed, 6 Sep 2023 12:27:07 +0530 Subject: [PATCH 2/5] Update README.md --- README.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index c9616b3..b4b5f8e 100644 --- a/README.md +++ b/README.md @@ -97,7 +97,7 @@ status: ## Minimum 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 resource usage data. The memory represents the minimum working set memory required, and for protocol and traffic engines, varies depending on the number of colocated ports. The figures are in Mi or MB. +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 resource usage data. The memory represents the minimum working set memory required, and for protocol and traffic engines, varies depending on the number of co-located ports e.g. when 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 does not include shared or cached memory across multiple containers/pods in a system. | --------------- | ------- | ------- | ------- | ------- | ------- | | Component | 1 Port | 2 Port | 4 Port | 6 Port | 8 Port | @@ -107,11 +107,12 @@ The minimum memory and cpu requirements for each ixia-c components are captured | --------------- | ------- | ------- | ------- | ------- | ------- | | Traffic Engine | 60 | 70 | 90 | 110 | 130 | | --------------- | ------- | ------- | ------- | ------- | ------- | - | Controller | 25 | | | | | + | Controller | 25* | | | | | | --------------- | ------- | ------- | ------- | ------- | ------- | - | gNMI | 15 | | | | | + | gNMI | 15* | | | | | | --------------- | ------- | ------- | ------- | ------- | ------- | - + +* 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. | ---------- | -------- | ------- | ---------- | ----- | @@ -121,11 +122,11 @@ The cpu resource figures are in millicores. | Min CPU | 200 | 200 | 10 | 10 | | ---------- | -------- | ------- | ---------- | ----- | -The operator sets the minimum memory requirement for each ixia-c component depending on the port configuration. The minimum cpu requirement is set to a default value for each component. +The operator sets the minimum memory requirement to the default value for each component, depending on the port configuration similar to what is shown in the table above, showing minimum memory requirements in different deployment configurations. The minimum cpu requirement is set to a default value for each component. -### Minimum resource usage based on various test configurations +### Minimum and maximum resource usage based on various test configurations -Depending on the nature of test run, the memory and cpu resource requirements may vary across all ixia-c components. The following tables capture the memory usage for lag scenarios with varying numbers of member ports. The minimum value represents initial memory on topology deployment and maximum value indicates the peak memory usage during the test run. Figures are in Mi or MB. +Depending on the nature of 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 initial memory on topology deployment and maximum value indicates the peak memory usage during the test run. Figures are in Mi or MB. | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | | Component | Min/Max | 1 Port | 2 Port | 4 Port | 6 Port | 8 Port | From ca658ef1ac05355facfde43e4498e7da4dfbacc7 Mon Sep 17 00:00:00 2001 From: anjan-keysight <84822148+anjan-keysight@users.noreply.github.com> Date: Wed, 6 Sep 2023 12:40:17 +0530 Subject: [PATCH 3/5] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b4b5f8e..e5e0553 100644 --- a/README.md +++ b/README.md @@ -112,7 +112,8 @@ The minimum memory and cpu requirements for each ixia-c components are captured | gNMI | 15* | | | | | | --------------- | ------- | ------- | ------- | ------- | ------- | -* Controller and gNMI have a fixed minimum memory requirement and is currently not dependent on number of test ports for the topology. +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. | ---------- | -------- | ------- | ---------- | ----- | From b412cad126b72e48c2e486b8acc21a63daf3631a Mon Sep 17 00:00:00 2001 From: anjan-keysight <84822148+anjan-keysight@users.noreply.github.com> Date: Fri, 8 Sep 2023 19:33:52 +0530 Subject: [PATCH 4/5] Update README.md --- README.md | 90 +------------------------------------------------------ 1 file changed, 1 insertion(+), 89 deletions(-) diff --git a/README.md b/README.md index e5e0553..47aa03d 100644 --- a/README.md +++ b/README.md @@ -95,95 +95,7 @@ status: state: DEPLOYED ``` -## Minimum 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 resource usage data. The memory represents the minimum working set memory required, and for protocol and traffic engines, varies depending on the number of co-located ports e.g. when 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 does not include shared or cached memory across multiple containers/pods in a system. - - | --------------- | ------- | ------- | ------- | ------- | ------- | - | Component | 1 Port | 2 Port | 4 Port | 6 Port | 8 Port | - | | Default | | | | | - | --------------- | ------- | ------- | ------- | ------- | ------- | - | 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 | Controller | gNMI | - | | Engine | Engine | | | - | ---------- | -------- | ------- | ---------- | ----- | - | Min CPU | 200 | 200 | 10 | 10 | - | ---------- | -------- | ------- | ---------- | ----- | - -The operator sets the minimum memory requirement to the default value for each component, depending on the port configuration similar to what is shown in the table above, showing minimum memory requirements in different deployment configurations. The minimum cpu requirement is set to a default value for each component. - -### Minimum and maximum resource usage based on various test configurations - -Depending on the nature of 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 initial memory on topology deployment and maximum value indicates the peak memory usage during the test run. Figures are in Mi or MB. - - | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | - | Component | Min/Max | 1 Port | 2 Port | 4 Port | 6 Port | 8 Port | - | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | - | | Max | 348 | 423 | 455 | 464 | 492 | - | Protocol | ------- | ------ | ------ | ------ | ------ | ------ | - | Engine | Min | 323 | 360 | 360 | 360 | 360 | - | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | - | | Max | 58 | 68 | 90 | 111 | 134 | - | Traffic | ------- | ------ | ------ | ------ | ------ | ------ | - | Engine | Min | 47 | 49 | 49 | 49 | 49 | - | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | - | | Max | 21 | 21 | 23 | 24 | 25 | - | Controller | ------- | ------ | ------ | ------ | ------ | ------ | - | | Min | 13 | 13 | 13 | 13 | 13 | - | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | - | | Max | 14 | 14 | 14 | 14 | 14 | - | gNMI | ------- | ------ | ------ | ------ | ------ | ------ | - | | Min | 7 | 7 | 7 | 7 | 7 | - | ---------- | ------- | ------ | ------ | ------ | ------ | ------ | - -Following is the memory usage variation with scaling in control plane. The variation is on the number of BGP sessions (1K, 5K and 10K), in a back to back setup. Figures are in Mi or MB. - - | ---------- | ------- | ------ | ------ | ------ | - | Component | Min/Max | 1K | 5K | 10K | - | ---------- | ------- | ------ | ------ | ------ | - | | Max | 516 | 906 | 1367 | - | Protocol | ------- | ------ | ------ | ------ | - | Engine | Min | 323 | 323 | 323 | - | ---------- | ------- | ------ | ------ | ------ | - | | Max | 53 | 149 | 259 | - | Controller | ------- | ------ | ------ | ------ | - | | Min | 12 | 12 | 12 | - | ---------- | ------- | ------ | ------ | ------ | - | | Max | 7 | 7 | 7 | - | gNMI | ------- | ------ | ------ | ------ | - | | Min | 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 RSVP-TE control plane. Figures are in Mi or MB. - - | ---------- | ------- | ------ | ------ | ------ | - | Component | Min/Max | 10 | 1K | 4K | - | ---------- | ------- | ------ | ------ | ------ | - | | Max | 58 | 59 | 95 | - | Traffic | ------- | ------ | ------ | ------ | - | Engine | Min | 47 | 47 | 47 | - | ---------- | ------- | ------ | ------ | ------ | - | | Max | 18 | 46 | 120 | - | Controller | ------- | ------ | ------ | ------ | - | | Min | 12 | 12 | 12 | - | ---------- | ------- | ------ | ------ | ------ | - | | Max | 10 | 17 | 28 | - | gNMI | ------- | ------ | ------ | ------ | - | | Min | 7 | 7 | 7 | - | ---------- | ------- | ------ | ------ | ------ | +Note: The operator sets the minimum cpu and memory requirement to the default value for each component, depending on the port configuration, based on the data captured [here](https://github.com/open-traffic-generator/ixia-c/blob/mkdocs/docs/prerequisites.md). ## Deployment From d8bd0f7af2405f2009c197bfa5536a0a9af808d2 Mon Sep 17 00:00:00 2001 From: anjan-keysight <84822148+anjan-keysight@users.noreply.github.com> Date: Wed, 13 Sep 2023 23:47:03 +0530 Subject: [PATCH 5/5] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 47aa03d..86a27fd 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,7 @@ status: state: DEPLOYED ``` -Note: The operator sets the minimum cpu and memory requirement to the default value for each component, depending on the port configuration, based on the data captured [here](https://github.com/open-traffic-generator/ixia-c/blob/mkdocs/docs/prerequisites.md). +Note: The operator sets the minimum cpu and memory requirement to the default value for each component, depending on the port configuration, based on the data captured [here](https://github.com/open-traffic-generator/ixia-c/blob/mkdocs/docs/reference_advanced_deployments.md). ## Deployment