Test №1

Introduction: The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all services, used two autoscaling groups, 1st with 3 Instance Type: c7g.large for okapi service and 10 Instance Type: r7g.xlarge for others services. Fixed Load (average case) MOBIUS test was run.

Objective: The objective of test was to evaluate the performance of the MCPT environment by applying the baseline configuration, while adjusting the CPU allocation for all services to 2 vCPUs. Additionally, the test aimed to assess the impact of using two distinct autoscaling groups with different instance types: c7g.large for the Okapi service and r7g.xlarge for all other services. By running the Fixed Load (average case) MOBIUS test, the goal was to determine if this modified configuration could achieve similar or improved performance compared to the baseline, while potentially optimizing resource allocation and cost.

Results: Almost all workflows shows significant performance degradation.

Test №2

Introduction: The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all services, used two autoscaling groups, 1st with 3 Instance Type: c7g.large for okapi service and 10 Instance Type: m6g.2xlarge for others modules. Fixed Load (average case) MOBIUS test was run.

Objective: The objective of this test was to maintain the use of m6g.2xlarge instances for the main modules, as in the Baseline configuration, while introducing a second autoscaling group with c7g.large instances specifically for the Okapi service. This setup aims to explore the performance and cost-effectiveness of separating the Okapi service onto a smaller instance type while keeping the main services on the larger m6g.2xlarge instances.

Results: We observed nearly identical performance results in over half of the workflows compared to the Baseline configuration.

Test №3

Introduction: The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all services, used two autoscaling groups, 1st with 3 Instance Type: c7g.large for okapi service and 10 Instance Type: m6g.2xlarge for others services. Fixed Load (average case) MOBIUS test was run (Repeat Test 2).

Objective: The objective of this test was to validate the consistency of performance observed in Test 2 by repeating the same configuration. 

Results: We observed nearly identical performance results almost for all the workflows compared to the Baseline configuration.

Test №4

Introduction:  The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all modules, used two autoscaling groups, 1st with 6 Instance Type: c7g.large, 3 of them for okapi service and other 3 for mod-cources, mod-sender, mod-tasks-list, mod-gobi, edge-dematic, mod-erm-usage, mod-eusage-reports, mod-notify, mod-data-import services and 10 Instance Type: r7g.xlarge for others modules. Fixed Load (average case) MOBIUS test was run.

Objective: The objective of this test was to add more services with lower activity levels to the first autoscaling group, increasing the number of c7g.large instances from 3 to 6. For the main services, r7g.xlarge instances were used with a total of 10 instances, which are more cost-effective compared to the Baseline configuration with r6g.4xlarge.

Results: We observed a better performance compared to previous test.

Test №5

Introduction: The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all modules, used two autoscaling groups, 1st with 6 Instance Type: c7g.large, 3 of them for okapi service and other 3 for mod-cources, mod-sender, mod-tasks-list, mod-gobi, edge-dematic, mod-erm-usage, mod-eusage-reports, mod-notify, mod-data-import services and 10 Instance Type: r7g.xlarge for others modules. Fixed Load (average case) MOBIUS test was run (Repeat Test 4).

Objective: The objective of this test was to validate the consistency of performance observed in Test 4 by repeating the same configuration.

Results: We confirmed performance improvements with this configuration, also a several workflows shoes better performance than in Test 4.

Test №6

Introduction: The Baseline MCPT Environment configuration was applied, and CPU=2 was set for all modules, used two autoscaling groups, 1st with 6 Instance Type: c7g.large, 3 of them for okapi service and other 3 for mod-cources, mod-sender, mod-tasks-list, mod-gobi, edge-dematic, mod-erm-usage, mod-eusage-reports, mod-notify, mod-data-import services and 10 Instance Type: r7g.xlarge for others modules. Fixed Load (average case without DE_Exporting MARC Bib records custom workflow, DE_Exporting MARC Bib records workflow, and OPIH_/oai/records workflow) MOBIUS test was run.

Objective: The goal of this test was to exclude several unstable workflows and observe whether their removal would have a noticeable impact on the performance of the remaining workflows. Specifically, by omitting the DE_Exporting MARC Bib records custom workflow, DE_Exporting MARC Bib records workflow, and OPIH_/oai/records workflow, the test aimed to assess if the stability and performance of the other workflows would improve under the same configuration.

Results: We observed minor performance improvements across almost all workflows. However, these improvements were not substantial. It appears that the observed effects are relatively small and can be attributed to a reduced overall load in the environment.

Instance CPU Utilization

Service CPU Utilization

Here we can see that okapi used 48k% of the CPU power of parameter CPU=2.

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 99%.

DB Connections

Max number of DB connections was 6010.

Top SQL-queries

Instance CPU Utilization

Service CPU Utilization

Here we can see that okapi used 45k% of the CPU power of parameter CPU=2.

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 99%.

DB Connections

Max number of DB connections was 5900.

Top SQL-queries

Instance CPU Utilization

Service CPU Utilization

Here we can see that okapi used 43k% of the CPU power of parameter CPU=2.

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 99%.

DB Connections

Max number of DB connections was 6200.