Table of Contents outline true
...
| Requests | Executions | Response Times (ms) | ||||
|---|---|---|---|---|---|---|
| #Samples | Error % | Average | 90th pct | 95th pct | 99th pct | |
| Check-In Controller MCPTController (MCPT) CPU=2 | 2480 | 0% | 490.49 | 579 | 666.9 | 1576.47 |
Check-Out ControllerMCPTController (MCPT) CPU=2 | 2407 | 0% | 1018.55 | 1139 | 1277 | 2246.72 |
Check-In ControllerController (QCP1) CPU=2 | 2214 | 0.63% | 583.78 | 659 | 702.25 | 880.35 |
Check-Out ControllerQCP1Controller (QCP1) CPU=2 | 2975 | 0.94% | 953.84 | 1077 | 1166.2 | 1448.48 |
Check-In Controller (QCP1) CPU=0 | ||||||
Check-Out Controller (QCP1) CPU=0 | ||||||
This table contains durations for Data Import tests.
| Job Profile | File | Duration (h:mm:ss) | Status |
|---|---|---|---|
PTF Create 2 (MCPT) CPU=2 | 25k.mrc | 0:15:21 | COMMITTED |
PTF Create 2 (MCPT) CPU=2 | 100k.mrc | 1:01:25 | COMMITTED |
PTF - Create 2 (QCP1) CPU=2 | 25k.mrc | 0:14:52 | COMMITTED |
PTF - Create 2 (QCP1) CPU=2 | 100k.mrc | 0:50:36 | COMMITTED |
PTF - Create 2 (QCP1) CPU=0 | 25k.mrc | 0:14:47 | COMMITTED |
PTF - Create 2 (QCP1) CPU=0 | 100k.mrc | 0:52:34 | COMMITTED |
Comparison
This graph shows the durations of all workflows compared between tests.
...
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
...
Resource utilization for Test №3
The Baseline MCPT Environment configuration was applied, the instance type was changed to x2gd.xlarge, the number of instances was changed to 6, and CPU=0 was set for all services.
Service CPU Utilization
Here we can see that mod-permissions used 20% of the absolute CPU power of the container instance.
...
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.
...
Resource utilization for Test №4
The Baseline MCPT Environment configuration was applied, the instance type was changed to x2gd.xlarge, the number of instances was changed to 8, and CPU=0 was set for all services.
Service CPU Utilization
Here we can see that okapi used 20% of the absolute CPU power of the container instance.
...
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 91%.
...
Resource utilization for Test №5
The Baseline MCPT Environment configuration was applied, the instance type was changed to x2gd.large, the number of instances was changed to 10, and CPU=0 was set for all services.TT
Service CPU 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 42%.
...
Resource utilization for Test №6
The Baseline MCPT Environment configuration was applied, the instance type was changed to r6g.xlarge, the number of instances was changed to 14 but 12 were used, and CPU=2 was set for all services.
Service CPU Utilization
Here we can see that okapi used 46000% CPU of unit power.
...
Inctanse CPU Utilization
Kafka metrics
DB CPU Utilization
DB CPU was 98%.
...
Resource utilization for Test №7
The Baseline MCPT Environment configuration was applied, the instance type was changed to r6g.xlarge, the number of instances was changed to 14, placement strategy was updated to "one task per host", and CPU=2 was set for all services.
Service CPU Utilization
Here we can see that okapi used 44000% 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.
...
Inctanse CPU Utilization
Kafka metrics
DB CPU Utilization
DB CPU was 98%.
DB Connections
Max number of DB connections was 5150.
DB load
Top SQL-queries
Resource utilization for Test №8
The Baseline MCPT Environment configuration was applied, the instance type was changed to x2gd.large, the number of instances was changed to 14, placement strategy was updated to "one task per host", and CPU=2 was set for all services.
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 53%.
DB Connections
Max number of DB connections was 3842.
DB load
Top SQL-queries
...
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 tenant
- 4 m5.2xlarge brokers in 2 zones
Apache Kafka version 2.8.0
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).
...