Multi-tier network latency test plan #16760
Open
+26
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
sm-xu
changed the title
r12f
reviewed
Feb 8, 2025
|
|
||
| ## Background | ||
|
|
||
| In Broadcom architecture, the Memory Management Unit (MMU) handles packet buffering and traffic management within the device. Each MMU consists of two Ingress Traffic Managers (ITMs). The first and last quarters of the ports reside in one ITM, while the second and third quarters reside in the other ITM. We will test the latency of traffic managed within a single ITM as well as traffic that traverses between the two ITMs. |
There was a problem hiding this comment.
avoid naming vendor's name here. the test is vendor agnostic.
r12f
reviewed
Feb 8, 2025
|
|
||
| In Broadcom architecture, the Memory Management Unit (MMU) handles packet buffering and traffic management within the device. Each MMU consists of two Ingress Traffic Managers (ITMs). The first and last quarters of the ports reside in one ITM, while the second and third quarters reside in the other ITM. We will test the latency of traffic managed within a single ITM as well as traffic that traverses between the two ITMs. | ||
|
|
||
| Cut-through packet forwarding mode is unsupported in SONiC. Store-and-forward is supported, but it can only be set in SAI. Config_db support is not in place. So no packet forwarding requirement in latency test. |
There was a problem hiding this comment.
Cut-through packet forwarding mode is unsupported in SONiC. Store-and-forward is supported, but it can only be set in SAI.
this is not true. we can just say, currently, we are testing with store-and-forward mode only.
|
|
||
| 5. Vary traffic rates from 50% to 100% of the line rate. Observe how latency changes in relation to packet loss. Note: Latency measurements may be skewed due to packet loss, as lost packets are counted as having infinite latency. This issue should be addressed to ensure accurate results. | ||
|
|
||
| 6. Categorize latency results into multiple bins based on time intervals. Count the number of packets within the following latency ranges: under 1500ns, between 1500ns and 1600ns, between 1600ns and 1700ns, ... ..., between 3900ns and 4000ns, above 4000ns. Analyze the distribution to better understand latency characteristics. |
There was a problem hiding this comment.
make a test metrics section and describes all the metrics requirements here.
|
|
||
| 4. Repeat the test with packet sizes ranging from 86 bytes to 8096 bytes to analyze how packet size impacts latency. | ||
|
|
||
| 5. Vary traffic rates from 50% to 100% of the line rate. Observe how latency changes in relation to packet loss. Note: Latency measurements may be skewed due to packet loss, as lost packets are counted as having infinite latency. This issue should be addressed to ensure accurate results. |
There was a problem hiding this comment.
we need to be specific on how to vary the traffic rates.
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation