IN PROGRESS

Table of Contents

...

Per

Jira Legacy
server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key PERF-293

the following tests were performed using the data export workflow (bulk edits, and edifacts) to determine what happens to the export workflows when mod-data-export-worker (with two nodes) fails and to what load can the exports run successfully?. 

Infrastructure

PTF -environment

• 10 m6i.2xlarge EC2 instances
• 2 instances of db.r6.xlarge database instances, one reader and one writer
• MSK
  • 4 m5.2xlarge brokers in 2 zones
  • auto.create-topics.enable = true
  • log.retention.minutes=120
  • 2 partitions per DI topics
• okapi (running tasks -3)
  • 1024 CPU units, 1360 MB mem
• mod-users (running tasks -2) 
  • 128 CPU units, 896 MB mem
• mod-data-export (running tasks -1) 
  • 1024 CPU units, 896 MB mem
• mod-data-export-spring (running tasks -1) 
  • 256 CPU units, 1844 MB mem
• mod-data-export-worker (running tasks -1) 
  • 256 CPU units, 1844 MB mem
• mod-notes (running tasks -2) 
  • 128 CPU units, 896 MB mem
• mod-agreements (running tasks -2) 
  • 128 CPU units, 1382 MB mem

Software Versions

• mod-data-export-worker: 1.4.10
• mod-data-export-spring: 1.4.5
• mod-agreements: 5.2.2
• mod-notes: 3.1.2
• mod-users: 18.3.0
• mod-inventory-storage-24.1.0
• mod-inventory-18.2.2
• mod-orders-12.4.3
• mod-orders-storage-13.3.3
• okapi-4.14.2

Test Runs (initial assumption of the data sets for combo testing)

Bulk edit files are located at https://github.com/folio-org/perf-testing/tree/Bulk-edit/workflows-scripts/Bulk-edit

Test results

 * - average job processing time for the number of records specified ( upload identifiers + editing)

Failover testing. The behavior of the workflows when 'killing' the module

...