...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Table of Contents |
|---|
Overview:
The purpose of this test is to compare results from two identical test runs on different environment. Find the reason of slownesses if any will be there.
Summary:
In this particular case BHS1 is faster than GCP1. And BHS1 even more stable than GCP1 as we saw mod feesfines fail due to out of memory exception during one of the tests.
Version:
- mod-inventory-storage:19.4.4
- okapi:4.3.3
- mod-feesfines:15.9.2
...
- mod-inventory-storage, mod-feesfines, okapi.
Results comparison:
| Test# | Env | Requests | Response times (Seconds) | |||||
| Total | KO | Req/s | 50th pct | 75th pct | 95th pct | |||
| 1 | BHS1 | GET /accounts?query=loanId==(loanUUID or loanUUID)&limit=2147483647 | 133815 | 0 | 74.339 | 0.112 | 0.136 | 0.214 |
| 2 | GCP1 | 44932 | 3372 | 24.959 | 0.414 | 0.467 | 0.560 | |
| 3 | BHS1 | 138052 | 0 | 76.693 | 0.111 | 0.138 | 0.243 | |
| 4 | GCP1 | 42342 | 0 | 23.521 | 0.419 | 0.468 | 0.553 | |
Test#1
Service CPU usage for relevant modules
Service memory usage for relevant modules
DB CPU usage:
Test#2
Service CPU usage for relevant modules
Service memory usage for relevant modules
As you can see there's a spike of CPU usage on mod-feesfines, and also there's a drop of memory usage on mod-feesfines. Exactly at this moment one of mod-feesfines container failed with "out of memory exception"