Update expressroute-troubleshooting-network-performance.md #110120
Conversation
Added note obtained from a recent case about throughput performance over a long distance link (from Denver DC to Virginia ExR circuit). By using the following description, we could obtain in a 2500km distance over 200mbps in a single session by tuning TCP Window. Cannot modify entire values as I don't have an ExpressRoute with 10gbps for testing and update the table accordingly: [!NOTE] While these numbers should be taken into consideration, they were tested using AzureCT which is based in IPERF in Windows via PowerShell. In this scenario, IPERF does not honor default Windows TCP options for Scaling Factor, and uses a way lower Shift Count for the TCP Window size. The numbers represented here were performed using default IPERF values and are for general reference only. By tuning IPERF commands with "-w" switch and a big TCP Window size, better throughput can be obtained over long distances, showing significantly better throughput figures. Also, to ensure an ExpressRoute is using the full bandwidth, it's ideal to run the IPERF in multi threaded option from multiple machines simultaneously to ensure computing capacity is able to reach maximum link performance and is not limited by processing capacity of a single VM.
|
@dantecit0 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 27c9632: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@duongau - can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Hello @dantecit0, I have passed this along to the PG team to review and get back to me about your addtion. Thank you! |
Thanks Duong! I have made a pull request also for the AzureCT tool to update the script to include the newer binaries for iPerf here: Azure/NetworkMonitoring#29 If that gets accepted and corrected maybe the note I put is useless but still the table is misleading for reference as numbers would still be wrong. Thanks!! |
|
@dantecit0, please reach out to Jon Ormand he is the person that owns that NetworkMonitor branch and should be able to merge your change in the other PR. |
|
Hello @dantecit0, have you been able to reach out to Jon Ormond to get that PR merged? |
|
Hi @dantecit0, I'll merge this PR for now. Please let me know when your other PR gets merge and then we can remove this note. #sign-off. |
articles/expressroute/expressroute-troubleshooting-network-performance.md
Outdated
Show resolved
Hide resolved
prmerger-automator
bot
added
do-not-merge
and removed
qualifies-for-auto-merge
ready-to-merge
labels
|
Learn Build status updates of commit 17dd809: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
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. For any questions, please:
|
|
Thanks Duong!
Didn't have much response but will keep trying.
Thanks!
Enviado desde Outlook para Android<https://aka.ms/AAb9ysg>
…________________________________
From: Duong Au ***@***.***>
Sent: Wednesday, July 5, 2023 8:54:15 PM
To: MicrosoftDocs/azure-docs ***@***.***>
Cc: Dante Stancato ((HE / HIM / HIS)) ***@***.***>; Mention ***@***.***>
Subject: Re: [MicrosoftDocs/azure-docs] Update expressroute-troubleshooting-network-performance.md (PR #110120)
Hi @dantecit0<https://github.com/dantecit0>, I'll merge this PR for now. Please let me know when your other PR gets merge and then we can remove this note. #sign-off.
—
Reply to this email directly, view it on GitHub<#110120 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKZSW62XMN53V5NZZ6G3RVDXOWZ5PANCNFSM6AAAAAAYRBUMNI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @duongau |
Added note obtained from a recent case about throughput performance over a long distance link (from Denver DC to Virginia ExR circuit). By using the following description, we could obtain in a 2500km distance over 200mbps in a single session by tuning TCP Window. Cannot modify entire values as I don't have an ExpressRoute with 10gbps for testing and update the table accordingly:
[!NOTE] While these numbers should be taken into consideration, they were tested using AzureCT which is based in IPERF in Windows via PowerShell. In this scenario, IPERF does not honor default Windows TCP options for Scaling Factor, and uses a way lower Shift Count for the TCP Window size. The numbers represented here were performed using default IPERF values and are for general reference only. By tuning IPERF commands with "-w" switch and a big TCP Window size, better throughput can be obtained over long distances, showing significantly better throughput figures. Also, to ensure an ExpressRoute is using the full bandwidth, it's ideal to run the IPERF in multi threaded option from multiple machines simultaneously to ensure computing capacity is able to reach maximum link performance and is not limited by processing capacity of a single VM.