Table of Contents outline true
...
- During the tests Parameter CPU=0 improved performance for a several workflows, like MSF_TC: mod search by auth query, MSF_TC: mod search by contributors, MSF_TC: mod search by title query and ULR_TC: Users loan Renewal Transaction.
No memory leaks, memory consumption was stable during all of the tests.
- Tests had 100% errors count for AIE_TC: Create Invoices, AIE_TC: Invoices Approve, AIE_TC: Paying Invoices, TC: Receiving-an-Order-Line, Unreceiving-a-Piece and Unreceiving-a-Piece Workflows because data was not regenerated.
Test Runs
| Test | Status |
|---|---|
| Test 1: The Baseline MCPT Environment configuration was applied, and CPU=0 was set for all modules, Fixed Load (average case) MOBIUS test was run. | Completed |
| Test 2: The Baseline MCPT Environment configuration was applied, and CPU=0 was set for all modules, Fixed Load (high load case) MOBIUS test was run. | Completed |
| Test 3: The Baseline MCPT Environment configuration was applied, and CPU=0 was set for all modules, Fixed Load (average case) MOBIUS test was run (rerun Test 1). | Completed |
| Test 4: The Baseline MCPT Environment configuration was applied, and CPU=1 was set for all modules, Fixed Load (average case) MOBIUS test was run. | Completed |
| Test 5: The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all modules, Check In\Check Out with 20 users for one tenant on 30 minutes test was run. | Completed |
| Test 6: The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all modules, Data Import - Create with 25k and 100k records files tests were run. | Completed |
| Test 7: The Baseline QCP1 Environment configuration was applied, and CPU=2 was set for all modules, Check In\Check Out with 20 users for one tenant on 30 minutes test was run. | Completed |
| Test 8: The Baseline QCP1 Environment configuration was applied, and CPU=2 was set for all modules, Data Import - Create with 25k and 100k records files tests were run. | Completed |
| Test 9: The Baseline QCP1 Environment configuration was applied, and CPU=0 was set for all modules, Check In\Check Out with 20 users for one tenant on 30 minutes test was run. | Completed |
| Test 10: The Baseline QCP1 Environment configuration was applied, and CPU=0 was set for all modules, Data Import - Create with 25k and 100k records files tests were run. | Completed |
Test Results
This table contains durations for all Workflows.
...
Service CPU Utilization
Here we can see that nginx-okapi modules used 20% CPU for Test-2 (high load case).
...
Here we can see that Memory exceed 113% of the unit power mod-data-export-b modules for Test-2 (high load case).
Kafka metrics
DB CPU Utilization
DB CPU was 99% average with ERW: Exporting Receiving Information
...
Here we can't see any sign of memory leaks on every module. Memory shows stable trend.
Kafka metrics
DB CPU Utilization
DB CPU was 99% average with ERW: Exporting Receiving Information
...
Here we can't see any sign of memory leaks on every module. Memory shows stable trend.
Kafka metrics
DB CPU Utilization
DB CPU was 64% maximum.
...
Service CPU Utilization
Here we can see that mod-source-record-storage-b used 72000% of the CPU power of parameter CPU=2.
...
Here we can't see any sign of memory leaks on every module. Memory shows stable trend.
Kafka metrics
DB CPU Utilization
DB CPU was 99%.
...
Here we can't see any sign of memory leaks on every module. Memory shows stable trend.
Kafka metrics
DB CPU Utilization
DB CPU was 57%.
...
Here we can't see any sign of memory leaks on every module. Memory shows stable trend.
Kafka metrics
DB CPU Utilization
DB CPU was 98%.
...
Test №9
The Baseline QCP1 Environment configuration was applied, and CPU=0 was set for all modules, Check In\Check Out with 20 users for one tenant on 30 minutes test was run.
Instance CPU Utilization
Service CPU Utilization
Here we can see that okapi used 15% of the absolute CPU power of the container instance.
Service Memory Utilization
Here we can't see any sign of memory leaks on every module. Memory shows stable trend.
Kafka metrics
DB CPU Utilization
DB CPU was 98%.
DB Connections
Max number of DB connections was 5150.
Test №10
The Baseline QCP1 Environment configuration was applied, and CPU=0 was set for all modules, Data Import - Create with 25k and 100k records files tests were run.
Instance CPU Utilization
Service CPU Utilization
Here we can see that okapi used 38% of the unit CPU power.
Service Memory Utilization
Here we can't see any sign of memory leaks on every module. Memory shows stable trend.
Kafka metrics
DB CPU Utilization
DB CPU was maximum 92%.
DB Connections
Max number of DB connections was 921.
...
PTF - Baseline MCPT environment configuration
- 14 m6g.2xlarge EC2 instances located in US East (N. Virginia)us-east-1
1 database instance, writer
Name Memory GIB vCPUs db.r6g.4xlarge
128 GiB 16 vCPUs - Open Search ptf-test
- Data nodes
- Instance type - r6g.2xlarge.search
- Number of nodes - 4
- Version: OpenSearch_2_7_R20240502
- Dedicated master nodes
- Instance type - r6g.large.search
- Number of nodes - 3
- Data nodes
- MSK ptf-KRaft-mode
- 2 brokers, kafka.m7g.xlarge brokers in 2 zones
Apache Kafka version 3.7.x
EBS storage volume per broker 300 GiB
- auto.create.topics.enable=true
- log.retention.minutes=480
- default.replication.factor=3
...
Baseline MCPT Environment configuration according to tunning environment from previous report: task count: 4 for services: mod-permissions, mod-search, mod-patron, mod-inventory, mod-inventory-storage, mod-circulation, mod-circulation-storage, mod-order, mod-order-storage, mod-invoice, mod-invoice-storage, for mod-users and mod-authtoken task count 6. Parameter srs.marcIndexers.delete.interval.seconds=86400 for mod-source-record-storage. Instance type: m6g.2xlarge. Instances count: 14. Database r6g.4xlarge, Amazon OpenSearch Service ptf-test: r6g.2хlarge.search (4 nodes).
...