JOURNAL / TOPIC TAG

Performance.

A performance improvement should make a defined experience better under stated conditions. This collection covers caching experiments, latency distributions, and the telemetry that distinguishes a faster successful response from a fast failure.

Put this topic into practice

Choose a representative workload and a useful comparison. Include quiet periods, bursts, cold starts, and errors. A global average may hide a small group of very slow requests, while a request hit ratio may hide large origin transfers. Keep the population and measurement boundaries visible.

  • Compare equivalent workloads.
  • Report tail behavior alongside ordinary requests.
  • Count the overhead of the optimization itself.

Connect these ideas with the Analytics overview. If the question spans several parts of the system, the guide directory offers a sequence through the related decisions.

Read about performance

Illustration of a latency distribution and the p95 and p99 percentiles

Why p95 and p99 latency matter for edge applications

Averages can hide the requests that make an application feel unreliable. Learn what p95 and p99 describe, how to measure complete user journeys, and how to compare regional traffic and latency distributions without misleading aggregation.

Abstract edge analytics dashboard connecting cache outcomes, latency distributions, and request traffic.

CDN analytics: turn edge logs into useful decisions

Useful CDN analytics connects cache behavior, latency, and errors to a clear operational decision. Learn to define trustworthy metrics, interpret request and byte hit ratios, manage sampling and privacy, and test changes with meaningful guardrails.