mean
The sum of all values divided by how many there are; what people usually call the average.
In more detail
For latency the mean blends a few very slow requests into a calm-looking number, so it can stay flat through a real outage. Averages of percentiles are meaningless, and objectives should be written as proportions of requests rather than as averages.
Examples
A mean is easy to compute but sensitive to outliers: one very large value pulls it up.In this course: A mean blends fast and slow requests into one number, so a few very slow requests can hide behind a healthy-looking average. Nine requests at ten milliseconds and one at a thousand have a mean of 109 milliseconds.Related terms
- median — The middle value when all observations are sorted: half are faster and half are slower.
- percentile — The value below which a given percentage of measurements fall; p99 latency is the time 99 in 100 requests beat.
- tail latency — The latency of the slowest requests, measured by high percentiles such as p99.
- standard deviation — A measure of how spread out a set of numbers is around their mean.
- z-score — How many standard deviations a value lies from the mean: 0 is exactly average, 3 is far above normal.
- peak load — The highest rate of traffic a system has to handle, as opposed to its average.
- latency — The time between asking for something and getting the answer back.
Taught in
- Throughput: Change Lead Time And Deployment Frequency — DevOps & Site Reliability Engineering
- The Four Keys History And Retiring MTTR — DevOps & Site Reliability Engineering
- Percentiles Rather Than Averages — DevOps & Site Reliability Engineering
- Metric Types: Summaries And Histograms — Full-Stack Observability: Metrics, Tracing & Logging
- Why A Histogram Beats An Average — Full-Stack Observability: Metrics, Tracing & Logging
- Rates And Increases Over Time — Full-Stack Observability: Metrics, Tracing & Logging
- Calculating Percentiles With histogram_quantile — Full-Stack Observability: Metrics, Tracing & Logging
- Dashboards That Answer Questions — Full-Stack Observability: Metrics, Tracing & Logging
- Six Minutes Nobody Saw: Prometheus In One Outage — Prometheus Certified Associate (PCA) Exam Prep
- Ninety Nine Percent Of What? SLIs, SLOs And SLAs — Prometheus Certified Associate (PCA) Exam Prep
- Observability Sprint: One Failed Checkout — Prometheus Certified Associate (PCA) Exam Prep
- A Week Without A Scrape: Configuration And Relabelling — Prometheus Certified Associate (PCA) Exam Prep
- Cart Versus cart: The Data Model And What A Scrape Returns — Prometheus Certified Associate (PCA) Exam Prep
- Off By Five: What Prometheus Is Not For — Prometheus Certified Associate (PCA) Exam Prep
- The Server That Would Not Die: Selecting Data — Prometheus Certified Associate (PCA) Exam Prep
- Four Thousand Requests Vanished: Rates And Derivatives — Prometheus Certified Associate (PCA) Exam Prep
- Fifteen Requests Nobody Saw: Aggregating Over Time — Prometheus Certified Associate (PCA) Exam Prep
- Fifteen Lines And No Answer: Aggregating Over Labels — Prometheus Certified Associate (PCA) Exam Prep
- Under A Second, On Average: Histograms — Prometheus Certified Associate (PCA) Exam Prep
- The Export That Failed Quietly: Timestamp Metrics — Prometheus Certified Associate (PCA) Exam Prep
- A Database You Cannot Recompile: Exporters — Prometheus Certified Associate (PCA) Exam Prep
- Milliseconds Versus Seconds: Naming Metrics And Labels — Prometheus Certified Associate (PCA) Exam Prep
- Instrumentation Sprint: Sixteen Calls On Code And Exporters — Prometheus Certified Associate (PCA) Exam Prep
- Twelve Green Panels: Dashboarding Basics — Prometheus Certified Associate (PCA) Exam Prep
- Alerting Sprint: Eleven Calls In Three Rounds — Prometheus Certified Associate (PCA) Exam Prep
- Seventy Seven Percent, Book Now? The Full Mock — Prometheus Certified Associate (PCA) Exam Prep
- One Week, Three Objectives: Final Review — Prometheus Certified Associate (PCA) Exam Prep
- SOC Operating Models, Tiers & Key Performance Metrics — Security Operations & Threat Hunting (SOC)
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- Threat Intelligence Platforms & STIX/TAXII Ingestion — Security Operations & Threat Hunting (SOC)
- Event Correlation Rules, Thresholds & Anomaly Pipelines — Security Operations & Threat Hunting (SOC)
- Log Parsing, Schema Normalization (OCSF/ECS) & Extraction — Security Operations & Threat Hunting (SOC)
- Detection as Code: Authoring & Testing Sigma Rules — Security Operations & Threat Hunting (SOC)
- Windows Event Logs, Sysmon & Linux Auditd Telemetry — Security Operations & Threat Hunting (SOC)
- YARA Rule Authoring & File Signature Matching — Security Operations & Threat Hunting (SOC)
- Cyber Kill Chain vs MITRE ATT&CK Framework — Security Operations & Threat Hunting (SOC)
- Adversary Tactics, Techniques & Procedures (TTP) Mapping — Security Operations & Threat Hunting (SOC)
- Indicator of Compromise Extraction & Threat Hunting Feeds — Security Operations & Threat Hunting (SOC)
- Tracking Advanced Persistent Threats & Profiles — Security Operations & Threat Hunting (SOC)
- Detecting Persistence: Tasks, Registry & Services — Security Operations & Threat Hunting (SOC)
- NIST SP 800-61 Incident Lifecycle & Management — Security Operations & Threat Hunting (SOC)
- Incident Triage, Severity Scoping & Communication — Security Operations & Threat Hunting (SOC)
- Recovery & System Validation Testing — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)
- Forensics Principles, Custody & Imaging — Security Operations & Threat Hunting (SOC)
- Memory Forensics: Process Trees & Injection — Security Operations & Threat Hunting (SOC)
- What A Design Is For, And How To Run A Design Discussion — Scalable System Design & Distributed Architecture
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- Latency Numbers Every Engineer Should Know — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture
- Partitioning, Sharding And Hot Keys — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Cache Invalidation And The Three Hard Cases — Scalable System Design & Distributed Architecture
- Queues, Events And Asynchronous Work — Scalable System Design & Distributed Architecture
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture
- Idempotency, And Exactly Once As A Fiction — Scalable System Design & Distributed Architecture
- Load Balancing And The Failure Modes It Introduces — Scalable System Design & Distributed Architecture
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- Capacity Planning As A Design Input — Scalable System Design & Distributed Architecture
- Worked Design One: Ticket Booking, Correctness First — Scalable System Design & Distributed Architecture
- Worked Design Two: A Global Chat System — Scalable System Design & Distributed Architecture
- Worked Design Two: Scaling Chat Fan Out — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture
- Load Testing: Percentiles Over Means — Automated Testing, TDD & Quality Engineering
References
- NIST/SEMATECH e-Handbook: measures of location (mean, median)
- Python documentation: statistics module
- Prometheus: histograms and summaries
- Python statistics module: mean
- Google SRE book: Service Level Objectives