[Optimization] Improve large_ip_packet_transmission_test performance by configuring all flows at once - #5803
Conversation
…all flows at once
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request optimizes the performance of the large IP packet transmission test suite. By batching flow configuration and leveraging granular traffic control states, the runtime is effectively halved. Additionally, the test lifecycle management has been improved by migrating cleanup operations to standard Go test cleanup hooks. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
Pull Request Functional Test Report for #5803 / 2a4caf0Virtual Devices
Hardware Devices
|
|
Please add the gemini skill for this inline with good and bad examples. |
There was a problem hiding this comment.
Code Review
This pull request refactors the large IP packet transmission tests to configure and start OTG protocols upfront, start/stop traffic on a per-flow basis, and utilize t.Cleanup for resource cleanup. The review feedback highlights a critical test isolation issue where physical cleanup is deferred until after the bundle tests because of how t.Cleanup is registered on the top-level t. Additionally, the feedback recommends removing the redundant 30-second static sleeps after PushConfig in both the physical and bundle test paths, as dynamic ARP resolution is already in place.
|
Please add labels and fix the gap analysis. |
Hi @navaneethyv - I have added the label. The gap analysis issue existed from before and is not the result of this PR. |
|
Shwetha the only MTU approver is not available yet , by passing on behalf. |
Changes here should reduce the runtime of the test by half without reducing test scope.