Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODDATAIMP-124

...

Testing results are better on the AWS environment because it has more computing power. 

...

Conclusions

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 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 Steps 4, 8, 9 and 13 on the diagram), waiting for the responses significantly slowed down the process. With Steps 4, 8 and 13 steps as batch operations it now requires 53 http requests calls to do the same. It is fair to assume that implementing batch save to mod-inventory-storage (step Step 9 at the diagram) will improve the data-import performance a bit more 

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODINVSTOR-291
 until the event driven approach is implemented. However, main improvements in performance are expected with applying of event driven approach
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1806
.