Networking Blog

The Official Blog Site of the Windows Core Networking Team at Microsoft

Options
32.9K
JamesKehr on Apr 18 2024 12:10 PM
8,196
tojens on Mar 07 2024 07:00 AM
5,985
tojens on Feb 06 2024 06:00 AM
1,699
Kyle Bisnett on Feb 02 2024 09:10 AM
11.4K
AditiPatange on Oct 25 2023 10:00 AM
10.9K
JamesKehr on Jul 05 2023 03:21 PM
4,438
Dan Cuomo on Jul 05 2023 10:13 AM
5,810
Dan Cuomo on Jun 09 2023 09:38 AM
5,240
Kyle Bisnett on Mar 16 2023 09:28 AM
9,608
Basel_Kablawi on Mar 15 2023 10:15 AM
6,884
Kyle Bisnett on Jan 17 2023 12:50 PM
5,740
Basel_Kablawi on Jan 06 2023 03:10 PM
7,836
Dan Cuomo on Nov 15 2022 06:01 AM
7,843
Dan Cuomo on Nov 15 2022 06:00 AM
6,357
Kyle Bisnett on Oct 12 2022 10:05 AM
15K
Daniel Havey on Sep 30 2022 08:50 AM
7,338
huanyi on Sep 16 2022 03:36 PM
11.5K
Dan Cuomo on Aug 31 2022 08:38 AM
7,318
Kyle Bisnett on Aug 30 2022 02:58 PM
6,868
Kyle Bisnett on Aug 25 2022 10:31 AM
52.4K
tojens on Jul 13 2022 10:00 AM
14K
nibanks on May 24 2022 09:56 AM
26.8K
tojens on Apr 22 2022 09:00 AM
72.2K
JamesKehr on Apr 04 2022 01:36 PM
9,843
tojens on Apr 01 2022 09:00 AM
30.9K
tojens on Oct 27 2021 06:00 AM
22.3K
nibanks on Oct 12 2021 12:40 PM
9,896
Dan Cuomo on Sep 27 2021 09:07 AM

Latest Comments

Sure, for MSFT only then MSFT tools are fine. Most networks now are a mix requiring tools that run on all platforms and systems. Iperf3 is designed for capacity tests and does say use iperf2. Yet most still use Iperf3 because 3 is larger than 2 and they don't understand the technical differences. Yo...
0 Likes
@rjmcmahon Please keep in mind that I am in support, so the article is support slanted. From a Microsoft supportability perspective, we need internally trusted tools like ntttcp and ctsTraffic that we (Microsoft support) can use for troubleshooting purposes when addressing networking issues related ...
0 Likes
@JamesKehr Hi James, It's not in the interests for a platform vendor to supply the tool to test their platform, particularly if that tool is platform or os specific. It has to be broadly accepted as reliable, open & transparent to code changes, and vendor independent. Iperf 2 goes back like 15 years...
0 Likes
Thanks again, @rjmcmahon ! In true Microsoft fashion, we have a separate tool just for latency called Latte. https://github.com/microsoft/latte https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-test-latency?tabs=windows
0 Likes
@JamesKehrYeah, it's a common misconception that a bigger number means better. In iperf's case, the number indicates different development teams with different goals. Iperf 3 is a misnomer as it's a not a follow on to the original iperf. Iperf 2 is based from the original code.I'd suggest trying ipe...
1 Likes