Table of Contents

Overview IN PROGRESS

...

• Data import create holdings job durations increased significantly in Quesnelia release. 4 times longer with 10k file. And not defined increasing in 80k file because it was stopped after 4 hours of test run with only 46 committed jobs (total for the test was 81).
• Top CPU utilization: mod-inventory-b - 16%, nginx-okapi - 5%, mod-source-record-storage-b - 4%, mod-quick-marc-b - 7%. Such low resource utilization from modules side can be explained by DB queries huge average latency during INSERT and UPDATE processes which had lock on the same tuple.
• Top memory consumption: mod-inventory-storage-b - 85%, mod-data-import-b - 52%, mod-source-record-storage-b - 45%, mod-source-record-manager-b - 43%. Growing trend was defined in tests set #1 for mod-inventory-storage-b - 85%
• DI job duration for the same file size grew from test to test if to use the same instance HRID to create holdings
• DI perform faster if to use files with 1 unique instance HRID for every 1000 records. DI duration corresponds to file size with such approach. Memory utilized without growing trend. CPU and RDS utilization increased because there are less locks in DB.

Recommendations & Jiras

• Investigate growing trend for mod-inventory-storage in tests set #1 (using 1 instance HRID to create all Holdings)
• Define high number of Holdings associated with one instance HRID that's still realistic

Errors

• error status for 32'd split job during 80k file importing- SNAPSHOT_UPDATE_ERROR

...

Set #2

Service CPU Utilization

...