| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
summary CICO requst times
CI-CO 8 users
CI-CO 8 users + SRS MARC Authority Data Import
CI-CO 20 users
CI-CO 8 20 users + SRS MARC Authority Data Import
Comparisons
Check-in-check-out response times are affected by data import. The response time is about 2x to 3x for check in and check out.
| 8 users | 8 users + 50KCreate SRS MARC Authority | 20 users | 20 users + 50KCreate SRS MARC Authority | |
|---|---|---|---|---|
| CI average | 0.591sec618s | 10.185sec867s | 0.617639s | 1.322136s |
| CO average | 1.059 sec22s | 21.087sec786s | 1.086 (33% errors*)159s | 2.230 (93%errors)054s |
| CI max | 12.656078s | 42.263959s | 1.625672s | 41.300888s |
| CO max | 2.114340s | 83.093329s | 2.450 (33% errors) | 6.633 (93%errors) |
...
| .7s | 3.697s |
With background activities, MARC Authority imports are slightly slower.
Profile | Standalone Import Durations | Data Import Durations with CICO | |
|---|---|---|---|
| 1K | Default - Create SRS MARC Authority | 40 sec | |
5K | Default - Create SRS MARC Authority | 1 min 14 sec | 2 min |
| 10K | Default - Create SRS MARC Authority | 2 min 32 sec | 4 min |
| 25K | Default - Create SRS MARC Authority | 6 min | 7 min |
| 50K | Default - Create SRS MARC Authority | 12 min | 13 min |
It's clear that (MARC Authority) data import affects check-in check-out response times much more than check-in check-out affects data import durations.
max resource usage for modules comparison with Data Import MARC Authorities (Lotus Snapshot)
test | module | CPU % | CPU % with CICO in background |
|---|---|---|---|
| 50k | mod-source-record-manager | 685 | 955 (139%) |
| 50k | mod-data-import-cs | 404 | 410 (101%) |
| 50k | okapi | 385 | 630 (163%) |
| 50k | mod-inventory | 235 | 270 (114%) |
| 50k | mod source-record-storage | 231 | 440 (190%) |
| 50k | mod-inventory-storage | 117 | 380 (324%) |
| 50k | mod-data-import | 111 | 260 (222%) |
...