TCP Throughput Calculator for Home Networks

April 29, 2026

TCP Throughput Calculator for Home Networks

Estimate goodput, see the bottleneck, and tune TCP for RTT, loss, MTU, and parallel streams.

📦Preset Scenarios
🔧Inputs
Use 1500 for standard Ethernet or 9000 for jumbo frames.
This is the round-trip time seen by the flow.
Small loss rates can sharply reduce TCP throughput.
Larger windows help long-RTT paths fill the pipe.
Multiple streams can soften window and loss limits.
Accounts for file format, compression, and app overhead.
Reserve room for retransmits, jitter, and headroom.
Visible for VPN and WAN presets where encapsulation matters.
Visible for Wi-Fi and mesh links with retry overhead.
Visible for jumbo-storage runs with large frames.
📈Results
Estimated TCP Throughput
--
Mbps
Per Stream Rate
--
Mbps
Window Ceiling
--
Mbps
Loss Ceiling
--
Mbps
🧱Equipment Spec Grid

1 GbE Desktop NIC

940 Mbps
TCP cap
92%
Offload
1-2
Streams
LAN copy
Best use

2.5 GbE NIC

2.35 Gbps
TCP cap
95%
Offload
1-4
Streams
NAS sync
Best use

10 GbE NIC

9.4 Gbps
TCP cap
97%
Offload
1-8
Streams
VM moves
Best use

Wi-Fi 6 Bridge

0.8 Gbps
TCP cap
80%
Offload
2-6
Streams
Burst copy
Best use

Wi-Fi 6E AP

1.2 Gbps
TCP cap
82%
Offload
2-8
Streams
Near AP
Best use

VPN Router

550 Mbps
TCP cap
70%
Offload
1-4
Streams
Remote
Best use

SSD NAS

2.0 Gbps
TCP cap
94%
Offload
2-6
Streams
Backup
Best use

HDD NAS

380 Mbps
TCP cap
88%
Offload
1-4
Streams
Media
Best use
📚Reference Tables
Mode Frame Cost Typical RTT When It Wins
Ethernet LANLow1-2 msBest baseline
Wi-Fi BridgeMedium3-10 msShort burst
VPN TunnelHigh15-60 msRemote access
Jumbo StorageVery low1-3 msBulk sync
MTU IPv4 MSS IPv6 MSS Notes
150014601440Default LAN
149214521432PPPoE path
900089608940Jumbo frames
120011601140Small tunnel
RTT Loss Single Stream Practical Fit
1 ms0.01%Very highLAN copy
5 ms0.05%HighSwitch hop
20 ms0.10%MediumWAN backup
50 ms0.50%LowRemote sync
Scenario Streams Target Main Limit
Backup copy1-2Stable rateWindow
VM migration2-4High burstLink cap
Remote sync2-6Steady flowLoss
Jumbo SMB1-8Bulk maxCPU

Tip: Raise the receive window first when RTT dominates the link.

Tip: Use jumbo frames only when every hop supports them.

Throughput with an Transmission Control Protocol (TCP) determine how much data will travel across the network. TCP throughput is typically less than the maximum speed of the network connection. People often expects there connection to allow data to be transferred at the maximum speed of the connection.

However, multiple factor limit the throughput of TCP. These factors include round-trip time, packet loss, and the size of the TCP receive window. Each of these factors limit the data that can travel over the network, but understanding these factors can allow people to manage the data that transmit over the network.

Why TCP Is Slower Than the Network and How to Fix It

Round-trip time is the length of time for a data packet to make its way from the source to the destination and for the acknowledgment signal to make its way back to the source. If the round-trip time for data to make its way from source to destination and back is high, the source has to wait a longer time before it can send another data packet. The high round-trip time creates a limitation on the TCP throughput of the data that transmits across the network.

The size of the TCP receive window limit the amount of data that can travel across the network. If the TCP receive window is too small, it will limit the amount of data that is sent across the network. Increasing the size of the TCP receive window allow more data to be sent across the network without having to wait for an acknowledgment signal from the destination.

By increasing the size of the TCP receive window, a high round-trip time can eliminate the limitation to some extent. Packet loss is another limitation on TCP throughput. Data packet may not reach their destinations, which force the network to retransmit the packets that were lost in transmission.

Loss of packets reduce throughput. Wireless networks may lose more packets than those on a wired network. Several TCP streams running in parallel can mitigate loss of packets.

Several TCP streams allow data to be transferred in a way that if one stream is lost, the others can continue the data transfer. TCP throughput is also limited by the hardware settings and the limitations of the hardware itself. One setting is the Maximum Transmission Unit, or MTU.

The MTU is the size of the data packet that is sent across the network. The standard size of the MTU is 1500 bytes. Many networks can be configured to use jumbo frames that allow the MTU to be increased to 9000 bytes.

Using jumbo frames can increase the throughput of TCP data because fewer data packet headers will have to travel across the network. However, every device on the network must be able to support jumbo frames. If any device do not support jumbo frames, the data packets will be fragmented, and this fragmentation will reduce the throughput of TCP data.

Additionally, the hardware on the network may also have limitations on the data that can travel across the network. For example, an older hard drive may be a part of a NAS device and may have a maximum transfer speed that is lesser than the network speed. In this instance, the older hard drive is a limitation on the TCP throughput of the data.

To increase the TCP throughput of a network, several steps can be taken. The round-trip time of the data can be checked. High round-trip time may require the increase of the size of the TCP receive window.

The packets that travel across the network can be checked for data loss. High rates of data loss may indicate that the use of parallel TCP streams should of been implemented. If the data is to remain within a local network and if all of the device on the network support jumbo frames, the use of jumbo frames can increase the throughput of the TCP data.

Each of these variables should be adjusted one at a time to observe there individual effect on the throughput of TCP data traveling across the network.

TCP Throughput Calculator for Home Networks

Related posts

Leave a Comment