Table of Contents outline true
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Summary
- Data Import tests finished successfully on qcon environment using the PTF - Updates Success - 2 profile and file with 25k records.
- Comparing with previous testing results Poppy and Quesnelia releases
- Data Import processed all jobs including test on 3 tenants concurrently without errors for Quesnelia releases.
- Data Import durations stayed in the same time range in Average for Quesnelia releases but it works stable and without errors.
- During testing, we noticed that mod-permission did not have any spikes and used 12% CPU for Quesnelia releases. For Poppy releases we had error.
...
| Profile | MARC File | DI Duration Quesnelia (hh:mm:ss) | Check In, Check Out Response time (8 users) Quesnelia | |
|---|---|---|---|---|
| CI Average sec | CO Average sec | |||
DI MARC Bib Create (PTF - Create 2) | 5K.mrc | 0:03:21 | ||
| 10K.mrc | 0:06:51 | |||
| 25K.mrc | 0:12:41 | |||
| 50K.mrc | 0:23:19 | |||
| 100K.mrc | 0:51:24 | |||
DI MARC Bib Create (PTF - Updates Success - 2) | 5K.mrc | 0:04:12 | ||
| 10K.mrc | 0:08:15 | |||
| 25K.mrc | 0:20:38 | |||
| 50K.mrc | 0:43:06 | |||
| 100K.mrc | 1:29:09 | |||
Check-in/Check-out without DI
| Scenario | Load level | Request | Response time, sec Quesnelia | |
|---|---|---|---|---|
| 95 perc | average | |||
| Circulation Check-in/Check-out (without Data import) | 8 users | Check-in | ||
| Check-out | ||||
Comparison
This table contains durations comparison between Poppy and Quesnelia releases.
...
- Test 1: Manually tested 5K, 10K, 25K, 50K, 100K consequentially (with 5 min pause) records files, DI (DI MARC Bib Create ) started on College tenant(cs00000int_0001) only, and CICO with 8 users on background.
- Test 2: Manually tested 5K, 10K, 25K, 50K, 100K consequentially (with 5 min pause) records files, DI (DI MARC Bib Update) started on College tenant(cs00000int_0001) only, and CICO with 8 users on background.
At the time of the test run, Grafana was not available. As a result, response times for Check-In/Check-Out were parsed manually from a .jtl files, using the start and finish dates of the data import tests. These results were visualized in JMeter using a Listener (Response Times Over Time).