Title level request report [LOTUS]
Overview
The purpose of this test is to measure performance of Title Level Request workflow. Take baseline numbers for future test. Find possible issues, bottlenecks.
Environment
- mod-circulation:23.0.1
- mod-circulation-storage:14.0.0
- mod-inventory:18.1.4
- mod-inventory-storage:23.0.2
- okapi:4.13.0
Summary
Below you can find results of 4 subsequent tests on create Title Level Request. Few notable observations:
- ERROR rate is low 0,0007% of all requests
- High response time at the beginning of a test were made by caching process.
- Call affected most by caching [get] /inventory/items (holdingsRecordId=="{holdingsRecordId}");
- "Failed to publish LOAN_DUE_DATE_CHANGED event: loan is null" Error, appears each time after making title level request CIRC-1503
- Duplicate request is defined during creating of a test script UICIRC-781
- No Memory leaks were defined
- CPU usage is without sudden spikes and anomalies.
- Average response times for 5 users tests (for create TLR, lookup user, retrieve instance data transactions (including all related calls)):
- While caching going
- Get instance transaction 8.159s
- Create TLR. 1.054s
- Get users 0.212 s
- After caching is done:
- Get Instance transaction 0.657s
- Create TLR. 0.820s
- Get users 0.160s
- While caching going
- Average response times for 1 users tests (for create TLR, lookup user, retrieve instance data transactions (including all related calls)):
- Caching is done:
- Get instance transaction 0.657
- Create TLR. 0.820
- Get users 0.160
Test results
On screenshot above you can see differences in response times with caching process and without it. (Spikes of response times).
Buffer cache ratio chart
At the beginning of a test cache being involved into process. It's expanding high response times at the beginning of a test
Also DRS CPU utilization is much higher when cache is involved.