Differences

This shows you the differences between two versions of the page.

--- public:99_annexes:annex-b-terms-and-definitions:p:performance_efficiency [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1
+++ public:99_annexes:annex-b-terms-and-definitions:p:performance_efficiency [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Performance Efficiency ======
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+Performance Efficiency is a [[public:99_annexes:annex-b-terms-and-definitions:q:quality_characteristic|Quality Characteristic]] concerning performance relative to the resources used under specified conditions.
+Performance Efficiency can apply to:
+  * A [[public:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solution]]
+  * A [[public:99_annexes:annex-b-terms-and-definitions:d:distributed_system|Distributed System]]
+  * A [[public:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
+  * A [[public:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Set]]
+  * A service
+  * A software component
+  * A hardware component
+  * An [[public:99_annexes:annex-b-terms-and-definitions:e:execution_facility|Execution Facility]]
+  * An Operational Resource
+  * Another subject performing work or consuming resources
+Performance Efficiency can concern:
+  * Response time
+  * Processing time
+  * Latency
+  * Throughput
+  * Transaction rate
+  * Event-processing rate
+  * Data-transfer rate
+  * Capacity
+  * Concurrency
+  * Resource utilization
+  * Storage utilization
+  * Network utilization
+  * Processor utilization
+  * Memory utilization
+  * Energy consumption
+  * Another performance or resource-use characteristic
+Performance Efficiency can identify:
+  * The evaluated operation
+  * The evaluated workload
+  * The applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
+  * The applicable [[public:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
+  * The applicable [[public:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resources]]
+  * The applicable resource limits
+  * The applicable measurement interval
+  * The applicable performance measures
+  * The applicable resource-consumption measures
+  * The measurement units
+  * The measurement precision
+  * The permitted tolerance
+  * The applicable DIDO [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
+  * The applicable [[public:99_annexes:annex-b-terms-and-definitions:v:validation_criteria|Validation Criteria]]
+  * The applicable [[public:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]
+  * Its [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
+  * Its [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
+  * Its [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
+Performance Efficiency can be evaluated using relationships such as:
+  * Work completed per unit of time
+  * Work completed per unit of processor utilization
+  * Work completed per unit of memory
+  * Work completed per unit of storage
+  * Work completed per unit of network capacity
+  * Work completed per unit of energy
+  * Response time under a specified workload
+  * Throughput under a specified resource allocation
+  * Maximum supported workload under specified performance constraints
+===== Definition =====
+//[[public:99_annexes:annex-b-terms-and-definitions:q:quality_characteristic|Quality Characteristic]] concerning performance relative to the resources used under specified conditions//
+===== Source =====
+Adapted from:
+  * [[https://www.iso.org/standard/78176.html|ISO/IEC 25010:2023, Systems and software Quality Requirements and Evaluation (SQuaRE) — Product quality model]]
+  * [[https://www.iso.org/standard/35747.html|ISO/IEC 25023:2016, Systems and software Quality Requirements and Evaluation (SQuaRE) — Measurement of system and software product quality]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:q:quality_characteristic|Quality Characteristic]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resource]]
+  * DIDO Reference Implementation Conceptual Model
+  * DIDO-TE draft Requirements Register
+ISO/IEC 25010 identifies Performance Efficiency as a product-quality characteristic concerning performance relative to the amount of resources used under stated conditions.
+ISO/IEC 25023 provides quality measures for quantitatively evaluating system and software-product quality characteristics and subcharacteristics.
+This definition adapts Performance Efficiency for DIDO-TE evaluation of Candidate Solutions and distributed-system subjects under controlled Test Environment, workload, Configuration, and resource conditions.
+===== Note =====
+Performance Efficiency differs from performance:
+  * Performance can identify an observed accomplishment, timing value, rate, or capacity
+  * Performance Efficiency relates performance to the resources used under specified conditions
+Performance Efficiency differs from [[public:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]] consumption:
+  * Performance Efficiency evaluates the relationship between performance and resource use
+  * Resource consumption identifies the amount of a Resource consumed
+Two Candidate Solutions can have equal throughput but different Performance Efficiency when one consumes more resources.
+Two Candidate Solutions can consume equal resources but have different Performance Efficiency when one completes more work.
+Performance Efficiency cannot be compared objectively unless the evaluation identifies:
+  * The operation or workload
+  * The Test Environment
+  * The Configuration
+  * The allocated Operational Resources
+  * The measurement interval
+  * The measurement method
+  * The measurement units
+  * The required precision
+  * The permitted tolerance
+A single performance measurement does not necessarily establish Performance Efficiency.
+For example, response time without corresponding workload and resource conditions does not provide a complete Performance Efficiency evaluation.
+A higher value does not always indicate greater Performance Efficiency:
+  * Higher throughput generally indicates greater efficiency under equivalent resource conditions
+  * Higher response time generally indicates lower efficiency under equivalent workload conditions
+  * Higher resource consumption generally indicates lower efficiency when performance remains equivalent
+The applicable Acceptance Criteria establish the interpretation and preferred direction of each measure.
+Performance Efficiency can include more specific characteristics concerning:
+  * Time behavior
+  * Resource utilization
+  * Capacity
+These characteristics can require separate glossary definitions when DIDO-TE requirements refer to them directly.
+===== Example =====
+DIDO-TE evaluates three Candidate Solutions using the same Test Definition, Test Environment, workload, Configuration, and allocated Operational Resources.
+For each Candidate Solution, DIDO-TE measures:
+  * Transactions completed
+  * Elapsed time
+  * Processor utilization
+  * Memory utilization
+  * Storage utilization
+  * Network utilization
+  * Energy consumption
+The Acceptance Criteria establish the measurement interval, units, precision, tolerances, and normalization rules.
+DIDO-TE uses the resulting Test Results to compare:
+  * Transactions per second
+  * Transactions per processor unit
+  * Transactions per unit of memory
+  * Transactions per unit of energy
+These comparisons provide Evidence concerning the Performance Efficiency of each Candidate Solution.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>