Test status: PASSED
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The general recommendation for report formatting:[Do not include the section in reports ]
...
Make the page full-width Set your Confluence page to full-width to utilize the entire space available. This makes your report more readable and gives more room for arranging content aesthetically.
...
Image wide 1600px. This width offers a good balance, ensuring that images are clear and detailed without causing excessive loading times or appearing too large on the page.
...
Further changes are welcome
Overview
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 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
[ A brief introduction about the content of the page:
What we are testing? Provide context of the test. Is it for a new service? Is it an experiment? Is it regression test?
Include major things like environment settings (ECS, non-ECS, Eureka, non-Eureka, w/RW split, etc…)
What are the goals of the testing? Ex: Want to see the effect of using a different ec2 instance type. If regression: to see how vB compares to vA
Include defined SLAs, if available
Reference the Jira(s)
...
Summary
[ A bulleted-list of the most important and relevant observations from the test results. What are the most important things the readers need to know about this testing effort? Some suggestions
...
For the baseline test the mod-source-record-manager version was 3.5.0 for the test with CI/CO it was 3.5.4. Maybe it is the reason why the time of Data Import with CI/CO is even better than without CI/CO.
...
Profile
...
Duration
KIWI (Lotus) without CICO
...
Duration
with CICO 8 users KIWI (Lotus)
...
Duration
Nolana without CICO
...
Duration
with CICO 8 users Nolana
...
CheckIn average (seconds)
...
CheckOut average (seconds)
...
Deviation From the baseline CICO response times
...
5K MARC BIB Create
...
PTF - Create 2
...
5 min, 8 min (05:32.264)
(08:48.556)
...
5 min
(05:48.671)
...
2 min 51 s
...
00:01:56.847
...
0.851
0.817
...
1.388
1.417
...
CI: 44%
CO: 51%
...
5K MARC BIB Update
...
PTF - Updates Success - 1
...
11 min, 13 min
(10:07.723)
...
7 min
06:27.143
...
2 min 27s
...
00:02:51.525
...
1.102
0.747
...
1.867
1.094
...
CI: 39%
CO: 36
Attach the link to the report from which the data for comparison was extracted.Attach the link to the report from which the data for comparison was extracted.
Test | Ramsons | Quasnelia | ||
---|---|---|---|---|
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
[Description of notable observations of memory utilization with screenshots(of all modules and involved modules) and tables]
...