...
Ticket:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Recommendations & Jiras
Add more CPU for
Summary
The total duration:
...
Data export | Instances | Holdings | Authority | ||||||
500, sec | 1000 , sec | 2000 , sec | 500 , sec | 1000 , sec | 2000, sec | 500 , sec | 1000 , sec | 2000, sec | |
Average duration | 83 | 426 | 1184 | 10 | 87 | 405 | 5,9 | 6,2 | 10,6 |
Minimal duration | 12 | 32 | 1372127 | 5 | 16 | 32 | 5,8 | 5,7 | 1,15 |
Maximal duration | 131 | 571 | 1271372 | 29 | 127 | 504 | 6,6 | 11,7 | 15,8 |
75t percentile | 114 | 539 | 1350 | 12 | 113 | 490 | 5,8 | 6,1 | 14,4 |
90t percentile | 126 | 553 | 1362 | 19 | 119 | 500 | 5,9 | 6,5 | 15,5 |
...
The duration of the longest data-export for holdings is 7 hours and 40 minutes, and 12 hours and 30 minutes for instances on 42nd tenants.
Recommendations & Jiras
Restart the tests DE_instances T2(Max) and DE_holdings T4(Max) with different POOL_SIZE, and BATCH_SIZE parameters to check Data-export duration improvement. [MDEXP-688] Make configurable params for Data-Export(POOL_SIZE, BATCH_SIZE) - FOLIO Jira (atlassian.net)
Restart Data-Import(Authority) test on mcpt to check how Kafka topics affect performance(found in the scope of data-preparation) [MODELINKS-213] Data-import process creating incorrect topics in Kafka - FOLIO Jira (atlassian.net)
...