Transfer Time Over 1 Gbps
Designed for high-throughput network planning
This page serves advanced users, IT teams, and business networks that operate around 1 Gbps links. It focuses on the gap between theoretical 1 Gbps line rate and real transfer behavior.
Theoretical vs practical at 1 Gbps
- Theoretical ceiling: 1 Gbps equals 125 MB/s before overhead.
- Protocol efficiency: framing, encryption, and retransmits reduce payload rate.
- LAN vs WAN: LAN can approach ceiling more often; WAN usually cannot.
- Storage limits: disk read/write rates can cap throughput below network capacity.
When large transfers are deadline-sensitive, measure end-to-end sustained speed across the exact path.
1 Gbps transfer scenarios
- Branch office sync: nightly transfer over routed corporate WAN.
- Server migration: multi-terabyte handoff between data center racks.
- NAS replication: scheduled snapshots over VPN tunnels.
- Cloud egress/ingress job: mixed internet and local transfer stages.
FAQ
Why do I only see 700-900 Mbps on a 1 Gbps link?
That range is common after protocol overhead and endpoint constraints, especially outside controlled LAN tests.
Does SMB/NFS protocol choice matter?
Yes. Different protocol stacks and settings can change practical throughput and latency sensitivity.
Should I model backups and restores separately?
Yes. Read vs write performance often differs by storage system and can change total duration.
Can CPU encryption overhead reduce throughput?
Yes. Encrypted tunnels and compression can become bottlenecks on older hardware.
Is Wi-Fi valid for 1 Gbps planning?
Not for strict deadlines. Wired links are more predictable for sustained high-throughput transfers.
How do I plan conservative estimates?
Use measured sustained throughput from production-like runs and add margin for contention.