| Table of Contents |
|---|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
- /oai/records?verb=ListRecords&apikey=[APIKey]&resumptionToken=[resumptionToken] - performing cyclically repeatedly, harvesting 100 records each time until there is no more data in [tenant]_mod_oai_pmh.instances table to harvest.
[resumptionToken] returning in initial call response and in each harvesting call until there is something no more records to harvest. When all data has being harvested - resumptionToken will not return with the response.
Environments to test on:
...
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
ICP1 (Iris) instances 756417 7252127 8072048 SRS records 597223 710371 1186613
| Counts | ICP1 (Iris) | IMTC1 (Juniper) | JCP1 (Juniper) |
|---|
| 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.
Resource usage
We observe different CPU usage on mod-inventory storage between JCP and IMTC. I think that i can be explained with different numbers of instances that have SRS records.
IMTC
JCP1
ICP1
