Skip to end of banner
Go to start of banner

GET /loan-storage/loans Test Report

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »



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
1101800BHS1
2101800GCP1



Results comparison:

BHS1 test run

Requests TotalReq/sResponse times (Seconds)
50th pct75th pct95th pct
BHS1GET /loan-storage/loans?(userId=={UserID} and status.name<>Closed)10604058.9070.1620.1990.263
GCP110972860.9570.1570.1910.250

GCP1 test run

RequestsTotalReq/sResponse times (Seconds)
50th pct75th pct95th pct
GET /loan-storage/loans?(userId=={UserID} and status.name<>Closed)10972860.9570.1570.1910.250



Delta

Response times (Seconds)
Min50th pct75th pct95th pct99th pctMax
-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:




  • No labels