Latency Through the Day

Synthetic inspection stages: Read, Activate, Compare.

Explore a fictional day of response times with two comparable data series.

Latency Through the Day

A single average can hide a changing workload. This fictional dataset compares two invented response-time series across eight points in a day. It is not a measurement of Stage.

Read the shape before the number

Both series rise around the middle of the day and decline later. The second series stays lower, but a chart alone cannot explain why: the difference could come from workload, implementation, or the choice of observations.

Loading current public media…Download dataset

Use Load chart to activate the view, inspect both series, and download the small CSV. Every data point has an explicit hour and unit.

Calculate one difference

At noon, the invented baseline is 115 ms and the candidate is 72 ms. The absolute difference is:

MathematicsRendering this equation locally; the complete source follows.115 - 72 = 43

The relative reduction is approximately MathematicsRendering this equation locally; the complete source follows.43 / 115 = 0.374. These are descriptive calculations on invented values, not a performance promise.

TimeBaselineCandidate
00:0048 ms42 ms
12:00115 ms72 ms
21:0059 ms46 ms

Ask better questions

  • Are the samples comparable?
  • Are outliers visible?
  • Which units are used?
  • Does a lower value change the reader's actual experience?

For categorical comparison, open Choosing a Cache Strategy. For the conceptual request path behind a measurement, return to Inside a Request Pipeline.

Inspection notes

The text, table, and source download remain useful without activating the chart. The mathematics should retain a readable fallback. Change the theme and browser width to compare line visibility and table layout.