PTF - Data Export Test Report (Quesnelia - Eureka)
Overview
This document contains the results of testing Data Export (MARC BIB) on the Eureka release of Quesnelia FOLIO. The goal is to compare the performances of Data Export on Eureka and non-Eureka environments and to highlight any observable differences in the KPIs.
PERF-866: [Quesnelia] [Eureka] Data Export (MARC BIB)Closed
Summary
Test Results
This table contains durations for Data Export with 2 job profiles.
Profile | CSV File | Central Tenant (fs09000000) | ||
|---|---|---|---|---|
Result | Result | Status | ||
DE MARC Bib (Default instances export job profile) | 1k.csv | 0:00:07 | 0:00:03 | COMPLETED |
100k.csv | 0:06:03 | 0:02:17 | COMPLETED | |
500k.csv | 0:09:03 | 0:04:25 | COMPLETED | |
DE MARC Bib (srs - holdings and items) | 1k.csv | 0:00:13 | 0:00:10 | COMPLETED |
100k.csv | 0:20:25 | 0:12:41 | COMPLETED | |
500k.csv | 0:38:21 | 0:38:53 | COMPLETED | |
Comparison
This table contains durations comparison between Quesnelia ECS, NON-ECS and Eureka environments.
Profile | Number of records | Quesnelia NON-ECS QCP1 | Quesnelia ECS | Quesnelia Eureka | DE Duration, DELTA QCP1/QECP1 |
h:mm:ss | h:mm:ss | h:mm:ss | h:mm:ss / percent | ||
DE MARC Bib (Default instances export job profile) | 1k | 0:00:02 | 0:00:05 | 0:00:03 | +0:00:01 |
100k | 0:02:17 | 0:04:24 | 0:02:17 | 0:00:00 | |
500k | 0:05:10 | 0:06:17 | 0:04:25 | -0:00:45 | |
DE MARC Bib (srs - holdings and items) | 1k | 0:00:04 | 0:00:05 | 0:00:10 | +0:00:06 |
100k | 0:05:13 | 0:05:58 | 0:12:41 | +0:07:28 | |
500k | 0:08:58 | 0:08:28 | 0:38:53 | +0:29:55 |
Test №1 - №2
Introduction: The Baseline QECP1 Environment configuration was applied, and CPU=0 was set for all modules.
Objective: The objective of these tests was to collect performance measurements for the data-export process across central tenant.
Results: During the test, we observed that the database was running a background process for Database, so we deactivated mod-fqm-manager. As a result, the repeated test showed a twofold improvement in performance.
Service CPU Utilization
Here we can see that mod-data-export used 28% CPU Instance Power in spike.
Service Memory Utilization
Here we can see that all modules show a stable trend.
DB CPU Utilization
DB CPU spike was 68%.
DB Connections
DB connections was 830.
Kafka metrics
OpenSearch Data Nodes metrics
DB load
Top SQL-queries
Test №3 - №4
Introduction: The Baseline QECP1 Environment configuration was applied, and CPU=0 was set for all modules.
Objective: The objective of these tests has to repeat previous tests after deactivated mod-fqm-manager.
Results: Results were collect for central tenant without any background processes for Database.
Instance CPU Utilization
Service CPU Utilization
Here we can see that mod-data-export used 28% CPU Instance Power in spike.
Service Memory Utilization
Here we can see that all modules show a stable trend.
DB CPU Utilization
DB CPU spike was 22%.
DB Connections
DB connections was 850.
Kafka metrics
OpenSearch Data Nodes metrics
DB load
Top SQL-queries
Appendix
Infrastructure
PTF - environment Quesnelia [Eureka] (qecp1)
11 m6i.2xlarge EC2 instances located in US East (N. Virginia)us-east-1 [Number of ECS instances, instance type, location region]
1 instance of db.r6.xlarge database instance: Writer instance
OpenSearch
domain: ptf-test
Number of nodes: 7
Version: OpenSearch_2_13_R20240520-P5
MSK - fse-tenant
4 kafka.m7g.xlarge brokers in 2 zones
Apache Kafka version 3.7.x
EBS storage volume per broker 300 GiB
auto.create.topics.enable=true
log.retention.minutes=480
default.replication.factor=3