Skip to content

Conversation

@xsatishx
Copy link
Contributor

@xsatishx xsatishx commented Nov 6, 2025

Added note about performance degradation for TCP flows exceeding 1.5 Gbps in a single TCP flow as mentioned in https://learn.microsoft.com/en-us/azure/virtual-wan/hub-settings

Its better to state that in the main page.

Added note about performance degradation for TCP flows exceeding 1.5 Gbps  in a single TCP flow as mentioned in https://learn.microsoft.com/en-us/azure/virtual-wan/hub-settings

Its better to state that in the main page.
@prmerger-automator
Copy link
Contributor

@xsatishx : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 0b280ff:

💡 Validation status: suggestions

File Status Preview URL Details
articles/virtual-wan/virtual-wan-about.md 💡Suggestion Details

articles/virtual-wan/virtual-wan-about.md

  • Line 115, Column 186: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/azure/virtual-wan/hub-settings' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@v-dirichards v-dirichards requested a review from Copilot November 6, 2025 15:57
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR clarifies the performance characteristics of Azure Virtual WAN hub routers by documenting a specific throughput limitation for single TCP flows. While the aggregate throughput is 50 Gbps, single TCP flows exceeding 1.5 Gbps may experience performance degradation.

Key Changes:

  • Added inline documentation about single TCP flow limitations
  • Included reference to detailed hub settings documentation

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@v-dirichards
Copy link
Contributor

@cherylmc

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Nov 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants