...

• 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

...

• Reference to Grafana dashboard(link will not work after 30 days) - http://carrier-io.int.folio.ebsco.com/grafana/d/q69rYQlik/jmeter-performance?orgId=1&var-percentile=95&var-test_type=baseline&var-test=mod-search&var-env=int&var-grouping=1s&var-low_limit=250&var-high_limit=700&var-db_name=jmeter&var-sampler_type=All&from=1649439816854&to=1649444031072

CPU and Memory Utilization

mod-search's CPU was reasonable at around 10% throughout the test run

mod-search memory is stable around 40% throughtout the test run

Image Added

1 User with background reindexing

...

http://carrier-io.int.folio.ebsco.com/grafana/d/q69rYQlik/jmeter-performance?orgId=1&var-percentile=95&var-test_type=baseline&var-test=mod-search&var-env=int&var-grouping=1s&var-low_limit=250&var-high_limit=700&var-db_name=jmeter&var-sampler_type=All&from=1649782951255&to=1649787290850

CPU and Memory Utilization

When we start reindexing mod-search linearly spikes to 90% max. Now with background reindexing running, when we start the JMeter script, the CPU stays stable at 90% throughout the test run. This means CPU performance dropped by 80% with background indexing. CPU drops back to normal after reindexing is complete.

Image RemovedImage Added

mod-search memory is stable at around 65% throughout the test run and also during background reindexing

Image Added

20 Users without any background reindexing

...

Out of ~69K requests, 31K requests had a response time > 700 milliseconds All these 31K requests were wildcard queries

• CPU and Memory Utilization

mod-search's CPU was reasonable at around 30% throughout the test run which is 20% more than 1 user. 

Memory is stable at around 65% throughout the test run

Image Added

• Reference to Grafana dashboard(link will not work after 30 days) - http://carrier-io.int.folio.ebsco.com/grafana/d/q69rYQlik/jmeter-performance?orgId=1&var-percentile=95&var-test_type=baseline&var-test=mod-search&var-env=int&var-grouping=1s&var-low_limit=250&var-high_limit=700&var-db_name=jmeter&var-sampler_type=All&from=1649944107574&to=1649948967673

...

Out of ~69K requests, 32K requests had a response time > 700 milliseconds All these 32K requests were wildcard queries

• CPU and Memory Utilization

CPU spikes linearly 40% as we start background reindexing. When we start the JMeter script run, the CPU continues to move upwards and reaches a max of 70%. Okapi also consumes resources but it is less than 40% which reasonable.

Image RemovedImage Added

Memory is stable at around 65% throughout the test run and also during background reindexing 

Image Added

• Reference to Grafana dashboard(link will not work after 30 days) - http://carrier-io.int.folio.ebsco.com/grafana/d/q69rYQlik/jmeter-performance?orgId=1&var-percentile=95&var-test_type=baseline&var-test=mod-search&var-env=int&var-grouping=1s&var-low_limit=250&var-high_limit=700&var-db_name=jmeter&var-sampler_type=All&from=1650032755868&to=1650036953158

...

1. Jira Legacy
   server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MSEARCH-331

    

2. Jira Legacy
   server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MSEARCH-337

...

• 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

...