In telecommunications, round-trip delay (RTD) or round-trip time (RTT) is the amount of time it takes for a signal to be sent plus the amount of time it takes for acknowledgement of that signal having been received. This time delay includes propagation times for the paths between the two communication endpoints. In the context of computer networks, the signal is typically a data packet. RTT is also known as ping time, and can be determined with the ping command.
End-to-end delay is the length of time it takes for a signal to travel in one direction and is often approximated as half the RTT.
Round-trip delay and bandwidth are independent of each other. As the available bandwidth of networks increases, the round trip time does not similarly decrease, as it depends primarily on constant factors such as physical distance and the speed of signal propagation.
Networks with both high bandwidth and a high RTT (and thus high bandwidth-delay product) can have very large amounts of data in transit at any given time. Such long fat networks require a special protocol design. One example is the TCP window scale option.
The RTT was originally estimated in TCP by:
where is constant weighting factor (). Choosing a value for close to 1 makes the weighted average immune to changes that last a short time (e.g., a single segment that encounters long delay). Choosing a value for close to 0 makes the weighted average respond to changes in delay very quickly. This was improved by the Jacobson/Karels algorithm, which takes standard deviation into account as well. Once a new RTT is calculated, it is entered into the equation above to obtain an average RTT for that connection, and the procedure continues for every new calculation.
- Age of Information
- Lag (video games)
- Latency (engineering)
- Minimum-Pairs Protocol
- Network delay
- Time of flight
- Round-trip delay time, Boulder, Colorado: National Telecommunications and Information Administration's Institute for Telecommunication Sciences, retrieved 2021-05-29
- Aron Brand (May 6, 2020), "How latency is killing your app performance". Medium.com.
- Brian Heder (May 6, 2014), "Are your pipes too big?", Network World, retrieved 2016-01-09
- Douglas E. Comer (2000). Internetworking with TCP/IP - Principles, Protocols and Architecture (4th ed.). Prentice Hall. p. 226. ISBN 978-0-13-018380-4.