| Jira Legacy |
|---|
| server | FOLIO Issue TrackerSystem Jira |
|---|
| serverId | 6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc |
|---|
| key | PERF-197 |
|---|
|
Overview
As was mentioned in Jira - there is huge performance degradation between releases iris - juniper. According to Jira - previously harvesting process of 350K records takes ±2 hour and now on Juniper release it takes 4 hours.
...
Harvesting of 350K records.
| ICP1 (Iris) | IMTC1 (Juniper) | JCP1 (Juniper) |
|---|
| Test 1 | 1 hr 47 min | 1 hr 14 min | 45 min |
|---|
| Test 2 | 1 hr 26 min | 1 hr 10 min | 42 min |
|---|
env
| Counts | ICP1 (Iris) | IMTC1 (Juniper) | JCP1 (Juniper) |
|---|
instances| Instances | 8,072,048 | 756,417 | 7,252,127 |
|---|
| SRS records | 1,186,613 | 597,223 | 710,371 |
|---|
Conclusions:
- As you can see from table above - we can say that Juniper release at least not slower than Iris release, or even faster.
- We can see slowness on IMTC1 env (it should be more powerful than others). However it's still better or the same as ICP1 (Iris).
- The only difference between IMTC1 and JCP1 is state of DB (different data set may affect the performance). Between IMTC1 and JCP1, the difference here is the proportion of SRS records relative to the instance records. IMTC1's harvesting time may be slower because there are more SRS records to process per instances than with JCP1 instances.
- We'll need additional tests on same data set but on different releases.
...