| Table of Contents |
|---|
...
This document contains the results of testing Data Import Create MARC holdings records in pre-Nolana to detect performance trends.
Jira Legacy server System JiraFOLIO Issue Tracker serverId 01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49 key PERF-343
Software versions
...
- 10 m6i.2xlarge EC2 instances (changed. In Lotus it was m5.xlarge)
- 2 instances of 'db.r6g.xlarge' database instances: one reader, and one writer
- MSK
- Broker type: kafka.m5.2xlarge
- Total number of brokers: 4
- Number of zones: 2
- Brokers per zone: 2
- auto.create-topics.enable = true
- log.retention.minutes=480
- default.replication.factor=3
- 2 partitions per DI topics
- mod-data-import:2.6.1
- 256 CPU Units
- 2048/1844 Hard/Soft memory limits (MiB)
- mod-data-import-converter-storage:1.15.1
- 128 CPU Units
- 1024/896 Hard/Soft memory limits (MiB)
- mod-source-record-storage:5.5.2
- 1024 CPU Units
- 1536/1440 Hard/Soft memory limits (MiB)
- mod-source-record-manager:3.5.4
- 1024 CPU Units
- 4096/3688 Hard/Soft memory limits (MiB)
- mod-inventory:19.0.1
- mod-inventory-b
- 1024 CPU Units
- 2880/2592 Hard/Soft memory limits (MiB)
- inventory.kafka.DataImportConsumerVerticle.instancesNumber=10
- inventory.kafka.MarcBibInstanceHridSetConsumerVerticle.instancesNumber=10
- kafka.consumer.max.poll.records=10
- mod-inventory-x
- 1024 CPU Units
- 2880/2592 Hard/Soft memory limits (MiB)
- inventory.kafka.DataImportConsumerVerticle.instancesNumber=10
- inventory.kafka.MarcBibInstanceHridSetConsumerVerticle.instancesNumber=10
- kafka.consumer.max.poll.records=10
- mod-inventory-b
- mod-inventory-storage:25.0.1
- mod-inventory-storage-b
- 1024 CPU Units
- 2208/1952 Hard/Soft memory limits (MiB)
- mod-inventory-storage-x
- 1024 CPU Units
- 2208/1952 Hard/Soft memory limits (MiB)
- mod-inventory-storage-b
- mod-search:1.8.0
- 400 CPU Units
- 2592/2480 Hard/Soft memory limits (MiB)
- mod-quick-marc:2.5.0
- 128 CPU Units
- 2288/2176 Hard/Soft memory limits (MiB)
Results
Summary
The duration of an 80k data import operation - MARC Holdings - shows a quite positive improvement: - 7 m 43 s.
However, the peak average CPU (mod-inventory) value of the Nolana release looks higher than Morning Glory (previous).
More detailed information about the duration time of the data import operation is in the following table:
test | file | duration_Morning_Glory | duraton_Nolana | Diff_absolute | Diff_percentage |
|---|---|---|---|---|---|
1 | 1k | 28s | 32.7 s | +5 s | + 18% |
| 2 | 5k | 1 m 48s | 4 m 20.8 s | +2 m 33 s | + 142% |
| 3 | 10k | 4 m 4s | 3 m 24.9 s | - 39 s | - 16% |
| 4 | 80k | 29 m 6 s | 21 m 22.6 s | - 7 m 43 s | - 27% |
...
| Morning Glory | Nolana | |
|---|---|---|
| CPU | Here CPU usage is not higher than 60% for all related modules.
|
The highest average value of CPU (mod-inventory) value is 73.9% at peak. |
| Memory | Concerning behavior behaviour on :
However the last test for 80K didn't show any memory growth for any of the modules, so maybe the growth of mem usage can be explained by the working conditions of these modules.
|
Increased memory usage was detected for:
|
| RDS CPU | RDS CPU usage reached 80% maximum during the test.
|
ncp3-db-3fv7zu8sfdn5-auroracluster-nysenxyhpwrd
|
...