liveBook · Manning

Mean

As explained in Rust Servers, Services, and Apps

Latency is the delay between an operation being initiated and its observable completion or response.

Latency is the delay involved in a request and its response. A round trip reflects both network latency and service latency, so a slow response can arise outside the service as well as within it. section 1.2.2

In web applications, latency matters alongside other service requirements:

  • Backend services aim for low and predictable latency, particularly for video streaming and online gaming. section 1.2
  • Network latency depends on factors such as transmission medium, distance, router efficiency, and bandwidth; service latency can reflect I/O delays, garbage collection, pauses, context switching, and serialization costs. section 1.2.2
  • Rust’s low-level hardware control, lack of a garbage collector or runtime, non-blocking I/O, and zero-cost abstractions are presented as contributors to low service latency. section 1.2.2

How Rust Servers, Services, and Apps covers it

How deep it goes
Distinguishes network from service latency and names contributing factors without detailing measurement or optimization procedures.
Examples
Uses video streaming, online gaming, and round-trip network requests as latency-relevant examples.
What you can do after
Understand how network and service factors contribute to request-response latency and why Rust is associated with low latency.
How it connects
Connects latency to network latency, service latency, asynchronous I/O, garbage collection, and concurrency.

Also explained in

Compare how 29 books explain mean →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Rust Servers, Services, and Apps. The section links point to the parts of the book it draws on.