Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue

...

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

Image RemovedImage Added


Image RemovedImage Added

DB CPU Utilization

...

Here we can't see any sign of memory leaks on every module. Memory shows stable trend.


Kafka metrics

Image RemovedImage Added

Image RemovedImage Added



DB CPU Utilization

...

                                                                                                                     

Top SQL-queries



Test №5

The The Baseline MCPT Environment configuration  was applied,  and and CPU=2  was set for all  servicesmodules,  Check In\Check Out with 20 users for one tenant on 30 minutes test was run.

Instance CPU Utilization

Image Added

Service CPU Utilization

Here we can see that mod-permissions used 18300% of the CPU power of the parametr CPU=2.

...

Here we can't see any sign of memory leaks on every module. Memory shows stable trend.


Kafka metrics

Image Added

Image Added




DB CPU Utilization

DB CPU was 64% maximum.

...

Max number of DB connections was 2112.

DB load

    Image Added                                                                                                                   

Top SQL-queries

Image Added


Test №6

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 Baseline MCPT Environment configuration was applied, and CPU=2 was set for all  servicesmodules,  Data Import - Create with 25k and 100k records files tests were run.

Instance CPU Utilization

Image Added

Service CPU Utilization

Here we can see that okapi used 20% that mod-source-record-storage-b used 72000% of the absolute CPU power of the container instance.parameter CPU=2.

Image Added

Service Memory Utilization

Here we can't see any sign of memory leaks on every module. Memory shows stable trend.

Image Added

Kafka metrics

Image Added


Image Added



DB CPU Utilization

DB CPU was 91%99%.

Image Added

DB Connections

Max number of DB connections was 4840.

Image Added

DB load

                                                                                                                    

...

Test №7

The Baseline MCPT Environment configuration was applied and CPU=2 was set for all services.

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

...

Test №8

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.

Instance CPU Utilization

...

Inctanse CPU Utilization


Kafka metrics






DB CPU Utilization

DB CPU was 98%.

...

Test №9

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.

Instance CPU Utilization


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



Test №10

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.

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 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


    NameMemory GIBvCPUs

    db.r6g.4xlarge

    128 GiB16 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
  • MSK tenant
    4 m5.2xlarge ptf-KRaft-mode
    • brokers, kafka.m7g.xlarge brokers in 2 zones
    • Apache Kafka version 2version 3.87.0x 

    • 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.2xlargeInstances count: 14Database r6g.4xlargeAmazon OpenSearch Service  ptf-testr6g.2хlarge.search (4 nodes).

...