| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODDATAIMP-124 |
|---|
|
...
Before concept of batch operations was introduced importing of 30,000 raw MARC records took about 38-40 min on the local environment. Performing steps 4, 8 and 13 at the diagram above with batch save/update dramatically drastically decreased the number of http requests between the modules. Before it took more then 200 requests to process a chunk of 50 records (steps 4, 8, 9 and 13 on the diagram), waiting for the responses significantly slowed down the process. With 4, 8 and 13 steps as batch operations it now requires 53 http calls to do the same. It is fair to assume that implementing batch save to mod-inventory-storage (step 9 at the diagram) will improve the data-import performance a bit more
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODINVSTOR-291 |
|---|
|
. However, main improvements in performance are expected with applying of
event driven approach.