Overview

This document contains the results of testing workflows Check-in/Check-out and Data Import for MARC Bibliographic records in the Quesnelia release with a new MSK instance type where zookeeper instances are not required. The main idea is to see how the kafka.m7g.2xlarge with KRaft mode affects FOLIO performance. Compared results for main workflows with different instance types: kafka.m5.2xlarge against kafka.m7g.2xlarge.

Ticket: PERF-936: Kafka KRaft ModeClosedPreview

Summary

• Comparing kafka.m5.2xlarge, zookeeper metadata mode against kafka.m7g.2xlarge, KRaft metadata mode

  • Tests with KRaft mode enabled utilize less CPU resources by brokers ((5% at least, for some broker - 13%) during CI/CO and during DI + CI/CO and at the same time the CPU utilizations are more balanced across the brokers compared to zookeeper mode

  • The previous test results  * showed that the performance actually the same for m5 and m7g clusters so m7g and m7g KRaft mode should perform the same way as well. Results for comparison **

  • Main workflows KPIs do not degrade in tests with Check-in/Check-out with Data import

  • No memory leaks. No errors during tests.

• Resource utilization

  • Service memory usage doesn't differ in tests with both MSK cluster

  • Service CPU utilization in Zookeeper mode: mod-inventory-b - 147%, mod-quick-marc-b - 81%, mod-di-converter-storage-b - 116%, nginx-okapi - 79% the rest of modules utilized less than 50%

  • Service CPU utilization in KRaft mode: mod-inventory-b - 133%, mod-quick-marc-b - 75%, mod-di-converter-storage-b - 103%, nginx-okapi - 75% the rest of modules utilized less than 50%

  • DB CPU was on level of 90% during tests with both MSK cluster

*Kafka Zookeeper mode - Data Import with Check-ins Check-outs (Quesnelia)[non-ECS] MSK instance type comparison

**Kafka Zookeeper Mode vs KRaft Mode MSK - instance type comparison

Test Runs 

Test Results

This table shows results of Check-In/Check-out and Data Import create and update jobs.

Check-in/Check-out without DI

Comparison

Data Import durations and Check-In/Check-Out response time comparison

• Data import durations fluctuate within a 10% range of the baseline (tests with Zookeeper metadata mode)

• Response times of CI/CO with Data import do not differ in both MSK clusters

Check-in/Check-out without DI

• Check-in/Check-out perform the same in both MSK clusters. The difference of response times is so small that it can be neglected.

MSK resource utilization (CPU)

Response time

MSK instance: kafka.m5.2xlarge

Open

MSK instance: kafka.m7g.2xlarge

Open

Service CPU Utilization

CPU utilization table