Estimate transfer time using the slowest realistic sustained rate across the source storage, connection, protocol, destination storage, and device processing.
Key takeaways
- Interface link speed and sustained payload speed are not the same.
- Thousands of small files can transfer much more slowly than one large file.
- Both source read speed and destination write speed must support the target rate.
Map the complete transfer path
A typical transfer may include source storage, a device bus, CPU work, a protocol, one or more network links, another device, and destination storage. Any stage can cap the final throughput.
- Source read performance
- Device and bus limits
- Network or cable link
- Protocol and encryption work
- Destination write performance
- Competing activity on either device
Link rate versus payload rate
A link specification describes raw signaling or negotiated capacity. Real file data shares that capacity with framing, control messages, acknowledgements, and sometimes retransmissions.
For planning, a measured sustained rate from a representative transfer is more useful than the interface headline. Use the same file type, direction, and device pair whenever possible.
Why small files are slower
Opening, naming, checking, and closing each file creates work that does not scale directly with byte count. Directory updates, metadata, latency, security scanning, and sync logic can dominate a workload containing many small files.
Estimate with the slowest sustained rate
Suppose the source can read at 500 MB/s, the network sustains 110 MB/s, and the destination writes at 300 MB/s. The network is the likely ceiling, so 110 MB/s is the sensible first input for the transfer-time estimate.
| Stage | Observed sustained rate | Likely bottleneck? |
|---|---|---|
| Source storage | 500 MB/s | No |
| Network path | 110 MB/s | Yes |
| Destination storage | 300 MB/s | No |
Improve the estimate before buying hardware
Measure first, change one component at a time, and confirm that the expected bottleneck actually moved.
- Test a single large file and a small-file folder separately.
- Check both transfer directions.
- Watch source and destination storage activity.
- Compare wired and wireless paths.
- Record sustained speed after the initial cache burst.
Use the numbers
Related calculators
Common questions
Questions, answered.
Why does speed fall after a fast start?+
Caches and write buffers can produce a short burst. Sustained speed appears after those buffers fill or the workload reaches a slower storage tier.
Should I enter Gbps or GB/s?+
Choose the unit shown by your measurement. Remember that one GB/s equals eight Gbps before overhead.
Can compression make a transfer faster?+
Sometimes. It can reduce bytes sent when data compresses well, but compression and encryption also require processing time.