saturation
How full a system’s most constrained resource is, such as its CPU, memory, connections or queue.
In more detail
Near saturation, requests start to queue, latency rises steeply and errors appear; that is the signal to find the bottleneck rather than add more callers. It is one of the four golden signals of monitoring, with latency, traffic and errors.
Related terms
- bottleneck — The single most constrained part of a system or process, which limits how fast the whole thing can go.
- throughput — How much work a system completes per unit of time, such as requests per second.
- latency — The time between asking for something and getting the answer back.
- error rate — The share of requests that fail, reported alongside latency so a fast result is not mistaken for a healthy one.
- CPU — The chip in a computer that runs program instructions; a machine can have several.
- four golden signals — Latency, traffic, errors and saturation: the four measurements every service should emit.
- utilization — The fraction of time a resource is busy.
Taught in
- Load Testing — Modern API Architecture: REST, GraphQL & gRPC
- Deployment Strategies: Rolling Updates — DevOps & Site Reliability Engineering
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Timeouts, And Avoiding Cascaded Failure — 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: Scaling The Ticket Booking System — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture