PERF-143 - Getting issue details... STATUS
Overview:
The purpose of these tests is to compare results from two identical test runs on different environment. Find the reason of slownesses if any will be there.
Summary:
Both tests shows almost same behaviour and passed without errors. DB CPU usage reach 100% due to high RPS rate. However there is a differences between usage of CPU in modules related to token cache.
Moreover we found that on BHS1 is missing index 2020-12-09 17:45:10.097,"WARNING: Doing LIKE search without index for patron_action_session.jsonb->>'patronId', CQL >>> SQL: patronId == abf9af79-4c57-4615-800f-bfa9303b6fa4 >>> lower(f_unaccent(patron_action_session.jsonb->>'patronId')) LIKE lower(f_unaccent('abf9af79-4c57-4615-800f-bfa9303b6fa4'))"
Version:
mod-circulation:19.2.7;
okapi:4.3.3;
mod-circulation-storage:12.1.4;
Tests:
Test # | Virtual Users | Duration (sec) | Env |
|---|---|---|---|
| 1 | 10 | 1800 | BHS1 |
| 2 | 10 | 1800 | GCP1 |
Results comparison:
BHS1 test run
| Requests | Total | Req/s | Response times (Seconds) | |||
| 50th pct | 75th pct | 95th pct | ||||
| BHS1 | GET /loan-storage/loans?(userId=={UserID} and status.name<>Closed) | 106040 | 58.907 | 0.162 | 0.199 | 0.263 |
| GCP1 | 109728 | 60.957 | 0.157 | 0.191 | 0.250 | |
Delta
| Response times (Seconds) | |||||
| Min | 50th pct | 75th pct | 95th pct | 99th pct | Max |
| -0,005 | -0,005 | -0,008 | -0,013 | -0,024 | -0,437 |
BHS1 Service CPU utilisation
GCP1 Service CPU utilisation
BHS1 Service Memory Usage
GCP1 Service Memory usage:
BHS1 RDS CPU usage:
GCP1 RDS CPU usage:
