Performance
| 🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions. |
1. Overview
The quality attribute defines the capability of a system to process any request within a restricted time interval, and provide the processing of the required requests number in the set time interval without an increase in the time defined for their processing.
The Registry Platform performance requirements are represented by two key metrics:
-
Latency — time delay between request sending and receiving system response (95th percentile)
-
Throughput — system channel; capacity, defined by the number of processed requests in a set time period
|
You can read more on performance testing in Performance testing section. |
2. Target metrics
When defining target values for the aforementioned metrics, the classification of Registries, operational conditions and expected workload is taken into account.
Metric |
Request type |
Target value |
|||
Production hours |
Peak hours |
Evening hours |
Shadow hours |
||
Latency (мс) |
Read operation (by key and one field, without requests to third-party Registries) |
|
|
|
|
Write operation |
|
|
|
|
|
Throughput (requests/second) |
Read operation |
|
|
|
|
Write operation |
|
|
|
|
|
Metric |
Request type |
Target value |
|||
Production hours |
Peak hours |
Evening hours |
Shadow hours |
||
Latency (ms) |
Read operation (by key and one field, without requests to third-party Registries) |
|
|
|
|
Write operation |
|
|
|
|
|
Throughput (requests/second) |
Read operation |
|
|
|
|
Write operation |
|
|
|
|
|
Metric |
Request type |
Target value |
|||
Production hours |
Peak hours |
Evening hours |
Shadow hours |
||
Latency (ms) |
Read operation (by key and one field, without requests to third-party Registries) |
|
|
|
|
Write operation |
|
|
|
|
|
Throughput (requests/second) |
Read operation |
|
|
|
|
Write operation |
|
|
|
|
|