Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #31

Merged
merged 5 commits into from
Sep 13, 2023
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
90 changes: 90 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,96 @@ 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 |
| ---------- | ------- | ------ | ------ | ------ |

## Deployment

Please make sure that the setup meets [Deployment Prerequisites](#deployment-prerequisites).
Expand Down
Loading