Skip to content

Commit 193ec71

Browse files
committed
/p/78: Wording changes
1 parent f4215fd commit 193ec71

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

_posts/2026/2026-02-16-bonding-iperf3.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -71,11 +71,11 @@ We cannot attach too much importance to the bond mode when testing bonding perfo
7171
| C | 1 | BBR | 1.11 Gbps | 935 Mbps | 0 | 0 | 8.87 MB | 7.67 MB |
7272
| C | 1 | CUBIC | 1.16 Gbps | 931 Mbps | 0 | 0 | 6.44 MB | 4.20 MB |
7373

74-
We first look at `balance-tlb` mode.
74+
We first look at TLB bond mode.
7575
As expected, with one single stream, it runs on only one slave interface (confirmed by watching `bmon -p eth0,eth1,bond0` during execution).
7676
And with the entire route being able to carry nearly 1.8 Gbps, there's no surprise that different congestion algorithms don't affect single-stream performance in all scenarios.
7777

78-
We then note the huge difference between the BBR and CUBIC algorithms.
78+
We then note the huge difference between the BBR and CUBIC algorithms in RR bond mode.
7979
Because destinations A and B both have a very low BDP, any fluctuation in latency hits hard on CUBIC in forms of out-of-order packet deliveries, which reflects clearly in the difference of retransmitted packets and the Cwnd size.
8080
In TLB mode, with only one active NIC, retransmission is kept low, but in RR mode it skyrocketed.
8181

0 commit comments

Comments
 (0)