...

1. In this workflow, we load test mod-search without and with ES background reindexing across 2 tenants for the Lotus release -

   Jira Legacy
   server System JiraFOLIO Issue Tracker columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49 key PERF-225

We tested with 1, 20 virtual users against 10 million Inventory records. 

...

• 7.2 million inventory records (7.3 Million instances, 7.8 Million holdings record, 8.9 Million items)
• 80 FOLIO back-end modules deployed in 166 ECS services
• 3 okapi ECS services
• 7 m5.xlarge  EC2 instances
• 1  writer db.r6g.xlarge 1 reader db.r6g.xlarge AWS RDS instance

High-Level Summary

...

mod-search is around 40% which is relatively stable. CPU spiked to 40% from 30% after starting background ES reindexing.

Image RemovedImage Added

Memory also looks stable at around 61%

...

JIRA tickets created as part of this investigation

1. Jira Legacy
   server System JiraFOLIO Issue Tracker serverId 01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49 key MSEARCH-331

    

2. Jira Legacy
   server System JiraFOLIO Issue Tracker serverId 01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49 key MSEARCH-337

Additional information

• Different permutations of random words and sentences were generated from https://www.mit.edu/~ecprice/wordlist.10000 

• Artifact stored http://carrier-io.int.folio.ebsco.com/artifacts?q=mod-search - mod-search.zip

...