In short
- Definition: The amount of resources, such as CPU, memory, energy or bandwidth, that a system consumes to handle a given workload.
- Goal: Deliver the required service while minimizing resource use, cost and environmental impact.
- Example S.M.A.R.T. requirement: Under 50 ms of CPU and 20 MB of memory per request at 1,000 requests per second.
1. Definition
As a non-functional requirement, efficiency describes how much CPU, memory, storage, energy or network bandwidth a system uses to handle a given workload [1], [2].
Measure resources per unit of business work. Totals hide whether the system is getting better or worse.Key takeaway
In ISO/IEC 25010:2023, it corresponds to performance efficiency, with sub-characteristics such as time behavior, resource utilization and capacity. Efficiency focuses on the resources, not only on speed [3].
Good efficiency requirements are expressed per unit of work: per request, per transaction, per user or per report. That makes them comparable as volumes grow.
2. Goal
The goal is to deliver the required service while using as few resources as possible, which lowers cost and environmental impact.
Inefficient software needs more servers, larger devices and more energy, and the waste grows with every new user.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| CPU time per request | Milliseconds | < 50 ms | Profiling and application metrics |
| Memory per request or instance | MB | < 20 MB per request | Monitoring under load |
| Energy or carbon per transaction | Wh or gCO2e per transaction | Decreasing year over year | Provider reports or the SCI method |
| Resource utilization at peak | % CPU and memory | 40% to 70% (no waste, no saturation) | Infrastructure monitoring |
The Software Carbon Intensity (SCI) specification from the Green Software Foundation expresses emissions as a rate per functional unit, which fits this per-unit approach [4].
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- API: “At 1,000 requests per second, each request shall use less than 50 ms of CPU and 20 MB of memory on average, measured in the reference load test.”
- Batch: “The nightly billing job shall process 1 million invoices using no more than 4 vCPU-hours.”
- Mobile: “The app shall not use more than 2% of battery per hour of active use on the reference phone.”
5. Questions to Ask Stakeholders
- Which resources are the most expensive or constrained: CPU, memory, energy, bandwidth?
- What is the unit of work we should measure against?
- Are there hardware limits on users’ devices?
- Are there sustainability or carbon reporting goals?
- What is the current baseline, if any?
- How will efficiency be checked in every release?
6. Common Pitfalls
- Optimizing too early. Measure first. Optimize the parts that really consume resources.
- Ignoring idle consumption. Servers and apps that run without work still use energy and money.
- Measuring totals only. Per-unit metrics show whether growth is efficient.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Performance — speed and efficiency often improve together, but can conflict.
- Memory Optimization — focuses on one key resource.
- Environmental Protection — efficient software reduces energy use and emissions.
- Cost — fewer resources mean lower bills.
- Resource Constraints — sets the limits within which efficiency must be achieved.
8. FAQ
Performance is about speed and throughput; efficiency is about the resources used to achieve it.
Use cloud provider reports, hardware power metrics or the Software Carbon Intensity method, expressed per unit of work.
Yes. Aggressive optimization can reduce readability or maintainability, so set targets that are good enough.
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. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [5] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [6] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [7] |
| CPU | Central processing unit | The main processor of a computer, which executes program instructions. | [8] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [9] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [10] |
| MB | Megabyte | Unit of data size, about one million bytes. | [11] |
| 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. | [2] |
| SCI | Software Carbon Intensity | Green Software Foundation method for measuring the carbon emissions of software per unit of work. | [12] |
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. | [13] |
| Baseline | Approved reference point (scope, schedule, cost or measurement) against which progress is compared. | [14] |
| Batch processing | Processing large groups of records together, often at night, rather than one at a time. | [15] |
| Carbon footprint | Total greenhouse gas emissions caused by an activity, expressed as CO2 equivalent. | [16] |
| Cloud | Computing resources (servers, storage, services) rented over the internet from a provider. | [17] |
| Load test | Test that simulates the expected number of users or requests to check how the system behaves. | [18] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [19] |
| Throughput | Amount of work a system completes per unit of time, such as requests per second. | [20] |
| Transaction | Unit of work, such as a payment or an order, that must complete fully or not at all. | [21] |
10. Sources and Further Reading
- [1] “Algorithmic efficiency.” Wikipedia. https://en.wikipedia.org/wiki/Algorithmic_efficiency (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] “Software Carbon Intensity (SCI) Specification.” Green Software Foundation. https://sci.greensoftware.foundation/ (accessed Nov. 18, 2026).
- [5] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [6] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [7] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [8] “Central processing unit.” Wikipedia. https://en.wikipedia.org/wiki/Central_processing_unit (accessed Nov. 19, 2026).
- [9] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [10] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [11] “Megabyte.” Wikipedia. https://en.wikipedia.org/wiki/Megabyte (accessed Nov. 19, 2026).
- [12] “Software Carbon Intensity (SCI) Specification.” Green Software Foundation. https://greensoftware.foundation/standards/sci/ (accessed Nov. 19, 2026).
- [13] “Bandwidth (computing).” Wikipedia. https://en.wikipedia.org/wiki/Bandwidth_(computing) (accessed Nov. 19, 2026).
- [14] “Baseline (configuration management).” Wikipedia. https://en.wikipedia.org/wiki/Baseline_(configuration_management) (accessed Nov. 19, 2026).
- [15] “Batch processing.” Wikipedia. https://en.wikipedia.org/wiki/Batch_processing (accessed Nov. 19, 2026).
- [16] “Carbon footprint.” Wikipedia. https://en.wikipedia.org/wiki/Carbon_footprint (accessed Nov. 19, 2026).
- [17] “Cloud computing.” Wikipedia. https://en.wikipedia.org/wiki/Cloud_computing (accessed Nov. 19, 2026).
- [18] “Load testing.” Wikipedia. https://en.wikipedia.org/wiki/Load_testing (accessed Nov. 19, 2026).
- [19] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [20] “Network throughput.” Wikipedia. https://en.wikipedia.org/wiki/Network_throughput (accessed Nov. 19, 2026).
- [21] “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 @awesome; inline photo by @gmph, both on Unsplash.








