...

• During the Data-Export tests we observe Error "java.lang.OutOfMemoryError: Metaspace", so parameters for data-export module were changed:
  
  • "memory": 1024 → 2304
  • "memoryReservation": 896 → 2048
  • -XX:MaxMetaspaceSize=128m → 256m
  • -Xmx768m → 1536m
• After upgrade Data-Export module all Data Export tests finished successfully on qcpt environment using the Default instances, authority, holdings export job profiles and Custom PTF Profiles.

• No memory leaks, memory consumption was stable during all of the tests.

• Database CPU usage varied up to a maximum of 26%

...

...

This table contains Data Export durations for Test Set №6. 

Service CPU Utilization

Here we can see that mod-data-export used 575% CPU in spike.that CPU did not exceed 95% for all of the modules.

Image Added

Service Memory Utilization

Here we can see that data-export module used 88% memory.'t see any sign of memory leaks on every module. Memory shows stable trend.

Image Added

Kafka metrics

Image RemovedImage Added

Image RemovedImage Added

DB CPU Utilization

DB CPU was MAX 20-22% for all tests.99% average with ERW: Exporting Receiving Information

Image Added

DB Connections

Max number of DB connections was 1500 5568 in avarage.

DB load

Top SQL-queries

...

...

maximum.

Image Added

Service CPU Utilization

Here we can see that okapi used 13% CPU in spike.

Image AddedService Memory Utilization

Here we can see that mod-data-export used 570% CPU in spike.

Service Memory Utilization

Here we can see that data-export module used 110% memory.'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 MAX 24-26% for Test 1 and 2, and MAX 16% for Test 2.99% average with ERW: Exporting Receiving Information

Image Added

DB Connections

Max number of DB connections was 22305788.

Image Added

DB load

 Image Added                                                                                                                    

Top SQL-queries

Image Added

...

Service CPU Utilization

Here we can see that mod-data-export permissions used 230% 20% CPU.

Image Added

Service Memory Utilization

Here we can see that mod-data-export used 108% memory .'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 20%64% maximum.

Image Added

DB Connections

Max number of DB connections was 2040.

DB load

Top SQL-queries

Image Added

...

...

Service CPU Utilization

Here we can see that mod-data-export used 325% CPU.

...

Here we can see that mod-data-export used 73% memory .

Kafka metrics

DB CPU Utilization

DB CPU was 22%.

...

Max number of DB connections was 2630.

DB load

Top SQL-queries

...

Here we can see that mod-data-export used 82% memory .

Kafka metrics

DB CPU Utilization

DB CPU was 25%.

...

Max number of DB connections was 1850.

DB load

Top SQL-queries

...

Here we can see that mod-data-export used 82% memory .

Kafka metrics

DB CPU Utilization

DB CPU was 25%.

...

Max number of DB connections was 3050.

DB load

Top SQL-queries

Appendix

Infrastructure

PTF - Baseline MCPT environment configuration

• 11 m6g.2xlarge EC2 instances located in US East (N. Virginia)us-east-1

• 1 database  instance, writer

  
  

  Name	Memory GIB	vCPUs	max_connections
  db.r6g.xlarge	32 GiB	4 vCPUs	2731

  
  

• Number of records in DB:
  •  cs00000001_0042
    • instances - 637243
  •  cs00000001
    • authorities - 55000
  •  cs00000001_0003
    • holdings  - 146704
    • instances - 148713
• 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 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

...

• Test 1: 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. Instances count: 14. Database r6g.4xlarge, Amazon OpenSearch Service  ptf-test: r6g.2хlarge.search (4 nodes).
• Test 2: The Baseline MCPT Environment configuration was applied, and CPU=0 was set for all modules.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.