In short
- Definition: The amount of work a system can process in a given time, such as transactions, requests or messages per second.
- Goal: Handle the expected volume of work within the required time.
- Example S.M.A.R.T. requirement: At least 2,000 transactions per second sustained for 1 hour with an error rate below 0.1%.
1. Definition
As a non-functional requirement, throughput states how much work a system must process in a given time, such as transactions, requests or messages per second [1], [2], [3].
Peak load is the only load that matters on the day it arrives.Key takeaway
Throughput is different from response time: a system can answer each request quickly yet collapse when many arrive at once. Both must be specified, and they are linked by queueing effects: as throughput nears capacity, waiting times rise sharply.
Little’s law gives a useful sanity check: the average number of requests in the system equals the arrival rate multiplied by the average time each request spends inside it [4].
2. Goal
The goal is to handle the expected volume of work, including peaks, within the required time and without errors.
Under-specified throughput leads to systems that pass functional tests but fail on the first busy day: payroll runs, sales events or month-end closing.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Sustained throughput | Transactions per second | ≥ 2,000 for 1 hour | Load test |
| Peak throughput | Transactions per second | ≥ 3,000 for 10 min | Spike test |
| Error rate under load | % of requests | < 0.1% | Load test results |
| Batch completion | Records per hour | ≥ 5 million | Batch job logs |
Always state the duration, the transaction mix and the acceptable error rate together with the rate itself.
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Sustained load: “The order service shall process at least 2,000 transactions per second for 1 hour with an error rate below 0.1%.”
- Peak load: “The system shall absorb a peak of 3,000 transactions per second for 10 minutes without losing messages.”
- Batch: “The nightly billing batch shall process 5 million records within a 2-hour window.”
5. Questions to Ask Stakeholders
- What is the expected average and peak volume?
- Which transactions make up the typical mix?
- How long do peaks last, and when do they happen?
- What growth is expected over the next 3 years?
- What error rate is acceptable at peak?
- Where will load tests run, and on which data?
6. Common Pitfalls
- A number without a duration. “2,000 TPS” for one second proves nothing.
- Testing with one transaction type. Real traffic mixes reads, writes and reports.
- Ignoring downstream systems. Your throughput is capped by the slowest dependency.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Response Time — speed of each individual request.
- Capacity — maximum load the system can hold.
- Scalability — growing throughput by adding resources.
- Performance — the broader quality that includes throughput.
8. FAQ
Bandwidth is the theoretical maximum of a channel; throughput is the work actually processed.
With load and stress tests that replay a realistic transaction mix for a defined period.
Not if response times or error rates degrade; the three must be read together.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [5] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [7] |
| TPS | Transactions per second | Number of operations a system completes each second; a common throughput measure. | [8] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Bandwidth | Maximum amount of data a connection can carry per second. | [9] |
| Batch processing | Processing large groups of records together, often at night, rather than one at a time. | [10] |
| Load test | Test that simulates the expected number of users or requests to check how the system behaves. | [2] |
| Log | Time-stamped record of events written by software, used for troubleshooting and audit. | [11] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [12] |
| Stress test | Test that pushes a system beyond normal load to find its breaking point. | [13] |
| Transaction | Unit of work, such as a payment or an order, that must complete fully or not at all. | [14] |
10. Sources and Further Reading
- [1] “Throughput.” Wikipedia. https://en.wikipedia.org/wiki/Throughput (accessed Nov. 18, 2026).
- [2] “Load testing.” Wikipedia. https://en.wikipedia.org/wiki/Load_testing (accessed Nov. 18, 2026).
- [3] “Monitoring Distributed Systems (the four golden signals).” Google SRE. https://sre.google/sre-book/monitoring-distributed-systems/ (accessed Nov. 18, 2026).
- [4] “Little’s law.” Wikipedia. https://en.wikipedia.org/wiki/Little’s_law (accessed Nov. 18, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 19, 2026).
- [8] “Transactions per second.” Wikipedia. https://en.wikipedia.org/wiki/Transactions_per_second (accessed Nov. 19, 2026).
- [9] “Bandwidth (computing).” Wikipedia. https://en.wikipedia.org/wiki/Bandwidth_(computing) (accessed Nov. 19, 2026).
- [10] “Batch processing.” Wikipedia. https://en.wikipedia.org/wiki/Batch_processing (accessed Nov. 19, 2026).
- [11] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [12] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [13] “Stress testing (software).” Wikipedia. https://en.wikipedia.org/wiki/Stress_testing_(software) (accessed Nov. 19, 2026).
- [14] “Database transaction.” Wikipedia. https://en.wikipedia.org/wiki/Database_transaction (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @jaredmurray; inline photo by @peek_a_boo_who, both on Unsplash.








