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.

Sign up for GitHub

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

Jump to bottom

Update the scale numbers for ExpressRoute gateway bypass scenario. #642

Merged
merged 3 commits into from
Nov 8, 2024
Merged

Update the scale numbers for ExpressRoute gateway bypass scenario. #642

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
85ad679
Update
r12f Nov 8, 2024
33ef2c3
Minor update.
r12f Nov 8, 2024
559dfe4
minor update.
r12f Nov 8, 2024
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
7 changes: 3 additions & 4 deletions documentation/express-route-service/express-route-gateway-bypass.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,13 +77,12 @@ The scaling requirement for PL redirect map are listed as below. The metrics are

| Metric | Requirement |
| ------ | ----------- |
| # of ENIs per DPU | 32 |
| # of ENIs per DPU (every 200G) | 32 |
| # of VNET mapping per ENI | 64K |
| # of PPS | 64M |
| VNET mapping change rate (CRUD) | (TBD) |
| # of VNI per ENI | 1 |
| # of MSEE source PA per ENI (v4 + v6, mixed) | 64 |
| # of fast path packets | Same as CPS. 3M per card. |
| # of tunnels | (TBD) |
| # of next hop in each tunnel | (TBD) |

### 4.2. Reliability requirements

Expand Down