load testing
Measuring how a system behaves while a chosen amount of traffic is sent to it, to find its latency, throughput and limits.
In more detail
Describe the workload before quoting a result: the operation mix, data size, concurrency and duration. Warm up first, change one pressure at a time, count errors and timeouts as failures, and run only against a system you own or a staging copy.
Example
In this course: Load tests need a separate traffic tool, not a unit test framework. Define the workload, warm up the system, hold a steady level, and record count, errors and several percentiles. A result without its scenario and environment cannot be reproduced.Related terms
- 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.
- percentile — The value below which a given percentage of measurements fall; p99 latency is the time 99 in 100 requests beat.
- workload — The work a system runs or handles, such as an application running on a platform or the traffic used in a performance test.
- saturation — How full a system’s most constrained resource is, such as its CPU, memory, connections or queue.
- rate limiting — Capping how many requests a client may make in a period of time, and rejecting or delaying the rest.
- per node capacity — The throughput one server or node sustains while staying inside its latency target, found by a load test.
- knee of the curve — The point where a small rise in load starts causing a large rise in waiting time.
- Locust — An open-source load testing tool in which user behaviour is written as Python code.
- k6 — An open-source load testing tool from Grafana Labs in which scenarios are written in JavaScript.
- JMeter — An Apache open-source load testing tool, written in Java, that builds test plans in a graphical editor.
Taught in
- Load Testing — Modern API Architecture: REST, GraphQL & gRPC
- Rate Limiting And Resource Consumption — Application Security & Threat Modeling for Engineers
- Capacity Planning As A Design Input — Scalable System Design & Distributed Architecture
- Load Testing: Percentiles Over Means — Automated Testing, TDD & Quality Engineering
- Code Review As A Quality Gate — Automated Testing, TDD & Quality Engineering