Enter network flow inputs
Use the fields below to estimate throughput, goodput, utilization, delay impact, and path efficiency from observed network traffic.
Example data table
| Scenario | Packets | Avg Packet Size | Duration | Capacity | Loss | Raw Throughput | Goodput |
|---|---|---|---|---|---|---|---|
| Branch file transfer | 120,000 | 900 bytes | 18 s | 100 Mbps | 0.8% | 48.00 Mbps | 44.07 Mbps |
| Voice traffic burst | 36,000 | 220 bytes | 8 s | 20 Mbps | 0.2% | 7.92 Mbps | 7.38 Mbps |
| Data center sync | 400,000 | 1200 bytes | 24 s | 500 Mbps | 1.1% | 160.00 Mbps | 146.11 Mbps |
Formula used
Total Bytes = Packet Count × Average Packet Size
Raw Throughput (Mbps) = (Total Bytes × 8) ÷ Duration ÷ 1,000,000
Goodput = Raw Throughput × (1 − Overhead%) × (1 − Loss%) × (1 − Retransmission%)
Packets Per Second = Packet Count ÷ Duration
Utilization (%) = Raw Throughput ÷ Link Capacity × 100
BDP (KB) = (Link Capacity in bps × RTT in seconds) ÷ 8 ÷ 1024
Window Adequacy (%) = TCP Window ÷ BDP × 100
The health score blends loss, retransmissions, jitter, utilization pressure, overhead, and delay into a practical quality indicator for rapid troubleshooting.
How to use this calculator
- Enter the number of packets seen in the measured flow.
- Provide the average packet size in bytes.
- Enter the observation duration in seconds.
- Set the link capacity to compare observed rate against available bandwidth.
- Enter protocol overhead, packet loss, and retransmission percentages.
- Provide average RTT, jitter, concurrent flows, and TCP window size.
- Click Analyze Network Flow to calculate throughput, goodput, utilization, BDP, and health score.
- Use the CSV and PDF buttons to export the calculated results.
Frequently asked questions
1. What does this calculator measure?
It estimates raw throughput, goodput, utilization, packet rate, BDP, TCP window adequacy, and likely bottlenecks using observed flow behavior and delivery conditions.
2. What is the difference between throughput and goodput?
Throughput reflects all transmitted bits. Goodput removes protocol overhead, loss, and retransmission penalties to estimate how much useful application data actually gets delivered.
3. Why does packet loss reduce goodput so much?
Loss forces recovery work and delays delivery. Even small loss values can lower effective transfer rates because transport protocols slow down and resend missing data.
4. Why is RTT included in the analysis?
RTT affects how much data must stay in flight to fill the path. High delay can limit performance when the TCP window is too small.
5. What does the bandwidth-delay product mean?
BDP estimates the amount of unacknowledged data required to fully use a link. It helps judge whether a send window is large enough for the path.
6. Can I use this for WAN and LAN traffic?
Yes. It works for both environments, but WAN paths usually show stronger RTT and loss effects, while LAN paths often reveal burst behavior and capacity limits.
7. How should I interpret the health score?
Higher scores indicate cleaner delivery and better efficiency. Lower scores usually point to loss, retransmissions, excessive jitter, high delay, or heavy utilization pressure.
8. Are these results exact?
They are analytical estimates based on average inputs. They are excellent for planning and troubleshooting, but packet captures and telemetry remain the final validation source.