PTF - Export deleted MARC authority records (Quesnelia) [ECS]
Overview
This document contains the results of testing of export deleted MARC authority records via API on the Quesnelia [ECS] release on qcon environment.
https://folio-org.atlassian.net/browse/PERF-897
Summary
Export deleted MARC authority records tests finished successfully on qcon environment using 100K, 300K and 646K records.
Comparing Test Duration and Response time between tests with 100K, 300K and 646K records
Test Duration grew up according to grew records count.
Response time for 100k and 300k records almost the same, but it grew up almost in two times compared 100k and 646k records.
During testing, we noticed that mod-entities-links module used 53% CPU in spikes for 300k, but for 646k records used 39% CPU.
No memory leaks are observed.
After the first part of the tests, the database was cleaned up by removing deleted MARC authority records. This cleanup negatively affected the duration and response time for the 100k records in the repeated test.
Test Runs
Test № | Scenario | Test Conditions | Results |
|---|---|---|---|
1 | Export deleted MARC authority records via API | 100k deleted records | Completed |
2 | 300k deleted records | Completed | |
3 | 646k deleted records | Completed |
Test Results
This table contains durations for export deleted MARC authority records and response time (Average) for GET authority-storage/authorities endpoint.
Profile | Test Conditions | Test Duration sec | Response time Average sec |
|---|---|---|---|
| |||
Export deleted MARC authority records via API | 100k | 13.317 | 0.261 |
300k | 29.109 | 0.288 | |
646k | 90.045 | 0.514 | |
Export deleted MARC authority records via API (repeated tests) | 100k | 25.892 | 0.512 |
300k | 36.173 | 0.358 |
Resource utilization for Test №1
Service CPU Utilization
Here we can see that mod-entities-links used 18% CPU in spikes.
Service Memory Utilization
Here we can see that all modules show a stable trend.
DB CPU Utilization
DB CPU was 12%.
DB Connections
Max number of DB connections was 1355.
DB load
Top SQL-queries
# | TOP 5 SQL statements |
|---|---|
1 |
|
2 |
|
3 |
|
4 |
|
5 |
|
Resource utilization for Test №2
Service CPU Utilization
Here we can see that mod-entities-links used 53% CPU in spikes.
Service Memory Utilization
Here we can see that all modules show a stable trend.
DB CPU Utilization
DB CPU was 23%.
DB Connections
Max number of DB connections was 1350.
DB load
Top SQL-queries
# | TOP SQL statements |
|---|---|
1 |
|
2 |
|
3 |
|
4 |
|