Back to articles
NDM-TCP: Correction, Clarification, and Real Performance Results
How-ToSystems

NDM-TCP: Correction, Clarification, and Real Performance Results

via Dev.toMuhammed Shafin P

Author: Muhammed Shafin P Date: 14th February 2026 Test System: Xubuntu 24.04 LTS, Linux Kernel 6.11.0 Important Correction and Apology I need to correct and clarify statements made in my previous article titled "NDM-TCP vs TCP Cubic vs TCP Reno: Bandwidth-Constrained Network Performance Analysis" which has been removed from publication. What I Got Wrong: The Cross-Connection Learning Claim The Incorrect Statement: In the removed article, I showed separate "Run 1" and "Run 2" tests and claimed NDM-TCP learned from the first run and improved performance in the second run. This was technically impossible and misleading. Why It Was Wrong: NDM-TCP's initialization function resets all internal state to zero every time a new TCP connection starts. Each separate iperf3 test creates a new connection, which means: All neural network state resets to zero No learning carries over between separate tests Performance differences were due to normal network variation, not learning The Missing Componen

Continue reading on Dev.to

Opens in a new tab

Read Full Article
6 views

Related Articles