...
- Define overall performance of POST /inventory-hierarchy/items-and-holdings;
- Find bottlenecks if possible;
- Measure KPI's for different number of instances included in request;
- Measure KPI's for different number of holdings attached per instance ID;
Overview
Mod-inventory-storage has a new API to gather all related instances' data, i.e., items and holdings, in one call in order to eliminate making 3 separate calls to get the data. The API also allows passing in x number of instance IDs to lookup. Since teams are now starting to use this API, it's important to understand the stability of the API with respect to the module's CPU and memory usage, and also the database usage.
Summary
- System shows stable work and quick responses in all test
- No memory leaks found
- There is a link between most used modules (see CPU) and test type. In case if it's extremely fast responses (for example for 5 holdings per instance and one user) - most used module will be mod-authtoken, otherwise (see test 4) that will be mod-inventory-storage. Same for increasing number of instances per request.
- DB CPU usage reaches maximum in 8-users test
- Fast response for most high load test (test 4). To extract an instance having 300+ holdings it takes 373 ms for 75th percentile. Therefore getting one holding with this endpoint takes 1.2 ms.
- No bottlenecks found.
Version:
"okapi-3.1.2";
"mod-inventory-storage-19.4.0-SNAPSHOT.448";
...
| Test | Virtual Users | Duration (min) | Instance per request | Holdings per instance |
|---|---|---|---|---|
| 1 | 1 | 30 | 1 | 5 |
| 2 | 2 | 30 | 1 | 5 |
| 3 | 1 | 30 | 1 (adding instance to request each loop) max - 964 | 5 |
| 4 | 1 | 30 | 1 | 300 |
| 5 | 1 | 30 | 50 | >1 |
| 6 | 8 | 30 | 50 | >1 |
| 7 | 1 | 90 | (adding 10 5 instance to request each loop) max - 5325 | >1 |
...