...
This document contains the results of the testing Data Import (batch imports) on 62 tenants with the following scenarios onthe MCPT cluster
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Central tenant: Large update imports - 2K; 30% Member tenants: single record imports (50% create, 50% update)
Central tenant: Large update imports - 10K; 100% Member tenants: single record imports (50% create, 50% update)
...
All Data-import finished with the status “Completed“
Most CPU consuming services were mod-consortia-b , mod-quick-marc-b, mod-inventory-b, mod-di-converter-storage-b, mod-source-record-storage-b, mod-inventory-storage-b, okapi-b, mod-source-record-manager-b it`s values are in Service CPU Utilization section
During 2 tests just 2 services showed changes in memory utilization: mod-data-import-b, mod-search-b, mod-inventory-b, mod-source-record-manager-b, mod-inventory-storage-b,mod-source-record-storage-b its values are in Service Memory Utilization section. No memory leaks.
DB CaPU usage during DI_T1(CT-2k_MT-SRI-50/50) has increased up to 80% and during DI_T2(CT-10k_MT-SRI-50/50) increased up to 95%.
Recommendations & Jiras
Add more CPU for 4 first services that have high CPU(>100%) utilization mod-consortia-b, mod-quick-marc-b, mod-inventory-b, mod-di-converter-storage-b
Test Results
DI_T1(CT-2k_MT-SRI-50/50). This section contains durations for Data-import for jobs with “PTF-Create-3” on Central tenant: with 2K records and single record imports on 21 member tenants (50% with “Inventory Single Record - Default Update Instance“ profile, 50% with “Inventory Single Record - Default Create Instance“ profile).
...