Test status: PASSED
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Regression testing of export of deleted MARC authority records via API. Measurement the performance of an export operation of 2K (paged) records for all 100K/300K deleted records
ECS environment with PTF data set
Classic PTF configuration with no additional improvements.
The purpose of this testing is to compare test results of Ramsons release with previous, Quasnelia release, check for improvements, possible issues/degradation.
Expected export duration - under a minute.
Jiras/ links:
Quasnelia Quesnelia release ticket:
. ReportJira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key PERF-897 Current ticket:
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key PERF-1028 Related to improvement task:
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MDEXP-769
...
Attach the link to the report from which the data for comparison was extracted.
Test | Ramsons | Quasnelia Quesnelia | ||
|---|---|---|---|---|
Duration (s/ ms) | GET_authority-storage/authorities response time (ms) | Duration (s/ ms) | GET_authority-storage/authorities response time (ms) | |
100K | 8s 652 ms | 178 ms | 13s 317 ms | 262 ms |
300K | 29s 989 ms | 216 ms | 29s 109 ms | 288 ms |
Memory Utilization
...
...
Nolana Avg
...
Nolana Min
...
Nolana Max
...
mod-circulation-storage
...
24%
...
23%
...
25%
...
mod-patron-blocks
...
34%
...
33%
...
Memory showed stable trend without visible signs of memory leaks or anomalies. Most used module is mod-entities-links and it consumes 32% memory in average during whole testing set. Please look on memory trend to all related modules in chart below.
Note: Taking into account that tests durations are less then a minute - in order to show trend, all tests included into chart. Below - table with top 3 modules
Module | Ramsons Avg | Quesnelia Avg |
|---|---|---|
mod-entities-links | 32% | 37% |
okapi | 32% | - |
mod-users | 25% | - |
CPU Utilization
[Description of notable observations of modules and eCPU utilization with screenshots (of all modules and involved modules) and tables]. Annotate graphs to show when a specific test started or ended, and select only the modules that are relevant to the test to show on the graphs]
In 100K and 300K tests CPU usage is barely visible because of fast test duration that’s why additional tests was performed (100K x10 and 300K x 10, basically same tests but 10 times one after another without pauses) to see if there are anomalies sudden spices, etc.. CPU usage stabilise on ±3%. CPU usage spiked only on mod-entities-links (as obvious), okapi, nginx-okapi and supportive services like mod-users-bl, mod-login, mod-authtoken.
No unexpected spikes or anomalies observed.
Note: Instance-level CPU usage is not included into this report as on instance scale CPU usage during this tests is not visible.
RDS CPU Utilization
[Description of notable observations of reader and writer instances CPU utilization with screenshots and tables, RDS Database connections, and other Database metrics]
...
Additional information from module and database logs (Optional)
...