⚙️ Technical details and optimization
General recommendations for configuring your PC to run RBTools. We strongly recommend making backups.
Alright, basement hackers 😎 Here are a few optimizations to get your rigs running at full throttle.
⏳ Reducing TIME_WAIT
By default, Windows keeps connections in TIME_WAIT for up to 240 seconds. It's better to reduce that to 30 seconds, so they're freed up faster.
PowerShell (not CMD):
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "TcpTimedWaitDelay" -Value 30 -PropertyType DWORD -Force
🔢 Increasing the number of available ports
PowerShell:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" -Name "MaxUserPort" -Value 65535 -PropertyType DWORD -Force
Check:
netsh int ipv4 show dynamicport tcp
If you see Start Port: 1024 and Number of Ports: 64512 — the range has been expanded successfully.
🧹 Clearing the socket cache and optimizing TCP
CMD:
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global rss=enabled
netsh int tcp set global chimney=enabled
netsh int tcp set global dca=enabled
⚡ Disabling ACK delays
CMD:
netsh int tcp set global ecncapability=disabled
netsh int tcp set global timestamps=disabled
After all the changes, restart your computer or server (dedicated server).
🔍 Checking connections
CMD:
netstat -an | find /c "ESTABLISHED"
Shows the number of established connections (ESTABLISHED) — active "client ↔ server" connections.
netstat -an | find /c "TIME_WAIT"
Shows the number of connections in state TIME_WAIT. If there are thousands of them (e.g. 15,000+), they clog the port pool and can cause the error:"Only one usage of each socket address..."