PTF - Data Export Test Report (Sunflower) [NON-ECS]
1 Overview
2 Summary
6 Appendix
6.1 Infrastructure
Overview
This document contains the results of three times testing Data Export (MARC BIB) on the Sunflower[NON-ECS] release. After one month of the first test, two additional tests were conducted. In the second test, mod circulation storage was enabled. In the third test, mod circulation storage on module was disabled. All test results have been summarized correctly.
https://folio-org.atlassian.net/browse/PERF-1115
Summary
Data Export tests finished successfully(except some duplications) on using the profiles Default instances export job profile and SRS - holdings and items job profile.
Comparing with previous results of Ramsons and Sunflower releases
Data Export processed all files including file with 500k records with negligible duplication errors in Sunflower env.
Data export durations are nearly twice as slow compared to Ramsons releases when mod circulation storage is enabled.
When mod circulation storage is disabled, it faster than run #1 and #2 but slower compared to Ramsons/
Test Results
This table contains durations for Data Export with two job profiles.
Profile | CSV File | Tenant (fs09000000) | |
|---|---|---|---|
Result | Status | ||
DE MARC Bib (Default instances export job profile) | 1k.csv | 0:00:09 | COMPLETED |
100k.csv | 0:06:03 | COMPLETED | |
500k.csv | 0:06:46 | COMPLETED | |
DE MARC Bib (SRS - holdings and items job profile) | 1k.csv | 0:00:17 | COMPLETED |
100k.csv | 0:12:20 | COMPLETED | |
500k.csv | 0:15:13 | COMPLETED | |
Comparison
This table contains durations comparison between Sunflower and Ramsons releases.
Profile | CSV File | DE Duration | DE Duration | DE Duration, DELTA Sunflower/Ramsons |
Result | Result | hh:mm:ss / percent | ||
DE MARC Bib (Default instances export job profile) | 1k.csv | 0:00:09 | 0:00:03 | +00:00:06 |
100k.csv | 0:06:03 | 0:02:19 | +00:03:44 | |
500k.csv | 0:07:49 | 0:04:33 | +00:03:16 | |
DE MARC Bib (SRS - holdings and items job profile) | 1k.csv | 0:00:17 | 0:00:06 | +00:00:11 |
100k.csv | 0:12:20 | 0:07:02 | +00:05:18 | |
500k.csv | 0:17:45 | 0:08:57 | +00:08:48 |
Resource utilization for Tests
Resource utilization table
CPU | RAM | ||
|---|---|---|---|
mod-data-export-b | 88.2% | mod-inventory-b | 78.3% |
mod-remote-storage-b | 13.7% | mod-data-export-b | 63% |
mod-inn-reach-b | 13.7% | mod-users-keycloak-b | 56.4% |
mod-audit-b | 11.3% | mod-audit-b | 55.1% |
mod-pubsub-b | 8.2% | mod-pubsub-b | 45.1% |
mod-users-keycloak-b | 7.8% | mod-quick-marc-b | 37.6% |
mod-inventory-b | 7.7% | mod-inn-reach-b | 31.8% |
mod-quick-marc-b | 7.4% | mod-invoice-storage-b | 31.8% |
mod-invoice-storage-b | 7.4% | mod-remote-storage-b
| 22.2% |
Instance CPU Utilization
Overview
This report compares the CPU utilization patterns observed during data export operations in the Ramsons and Sunflower environments. The purpose is to highlight performance differences and identify potential reasons why the Sunflower environment is approximately 2x slower in completing data exports, particularly for larger datasets.
Key Observations
Ramsons Environment
14:35: A 100k record export (Default profile) caused a minor CPU uptick (~5%).
14:45: A 500k export (Default profile) triggered a sharp spike in CPU usage—peaking around 26% on one instance.
15:10: Another 500k export using the SRS holdings and items profile resulted in a second peak—up to ~35.6%.
Performance: The spikes were short-lived, and CPU usage returned to baseline quickly, indicating efficient processing and resource handling.
Sunflower Environment
07:40–08:15: Two 100k exports (one Default, one SRS) led to mild CPU fluctuations.
08:20: A 500k export (Default profile) caused a moderate CPU spike (~21%).
09:15–09:25: A 500k export (SRS profile) resulted in sustained CPU utilization across multiple instances, peaking around 21.5%, but lasting nearly 10 minutes.
Performance: CPU load was more prolonged and distributed across instances. The system took significantly longer to complete the exports.
Conclusion: Sunflower Is Slower (~2x) Compared to Ramsons
Although Ramsons shows higher CPU peaks during export jobs, it consistently completes the tasks in shorter time frames. Sunflower, on the other hand, exhibits lower peak CPU but longer sustained utilization, indicating slower job execution. This aligns with the observation that Sunflower is approximately 2x slower in completing large export tasks.
Service CPU Utilization
Here we can see that mod-data-export used 88% CPU in spike.
Observation Timeframe: 07:30–09:30 UTC
Key Metrics:
100k export (Default and SRS):
Both operations push CPU usage above 10%, higher than Ramsons under similar load.
Indicates that even smaller exports in Sunflower require more CPU time.
500k export (Default):
mod-data-export-bspikes dramatically to ~88%, more than double Ramsons' peak for the same job.The spike is also sustained for ~5–6 minutes, rather than short and sharp.
500k export (SRS):
CPU usage hovers between 50–65% across services for over 10 minutes.
Clearly shows longer processing time and more sustained system pressure.
Interpretation:
Sunflower shows consistently higher and longer-lasting CPU usage, implying slower processing and less efficient handling of the export workload.
we got lower result after test1 so test 2 and 3 were conducted
What is test #1, #2?