In addition to ordinary windows on tcp, there is a CTCP.
It said to enhance the throughput in the case of long delay.
win7 can easily through netsh int tcp set global congestionprovider = ctcp provided.
win10 can not by netsh set, only through the power shell, ps settings.
ps in using a NetTCPsetting, but according to the following link, and that this win10 client operating system can not be modified NetTCPsetting parameters, because it is read-only. It can only be set on the server.
https://docs.microsoft.com/en-us/powershell/module/nettcpip/set-nettcpsetting?view=win10-ps
The Set-NetTCPSetting cmdlet modifies a TCP setting. TCP settings are optimized for different network conditions including latency and congestion. To apply a TCP setting to a port number or destination IP address range, create a transport filter by using the New-NetTransportFilter cmdlet.
Note
- You can modify Custom and Non-Custom settings on windows server 2016 and 2019.
- You can modify only Custom settings, Internet and Datacenter settings Cannot be modified on windows 2012 or earlier versions.
- You cannot modify the NetTCPsetting on Client Operating systems(Windows 7, 8.1 and 10) as they are Read-Only.
-CongestionProvider
Specifies the congestion provider property that TCP uses. The acceptable values for this parameter are:
- CTCP. Compound TCP increases the receive window and amount of data sent. CTCP can improve throughput on higher latency connections.
- DCTCP. Data Center TCP adjusts the TCP window based on network congestion feedback based on Explicit Congestion Notification (ECN) signaling. DCTCP may improve throughput on low latency links.
- Default. Servers use DCTCP by default. Client computers use NewReno. For information about NewReno, see RFC 3782.
Well, since not modify the template parameters.
How that specify which template to use it?
A post