PERF-131 - Getting issue details... STATUS

Overview

The purpose of this test is to define baselines of request search flow to be able compare test metrics in the future

Version

• okapi:4.2.2
• mod-inventory-storage:19.5.0-SNAPSHOT.460
• mod-circulation:19.2.2"
• mod-users:17.2.1"
• mod-circulation-storage:12.1.0

Tests

Test Summary

All tests shows stable work, and pass whit 0% of errors. However high CPU utilisation from RDS side may cause an issues with bigger loads in future. 

The more load causes more CPU usage on database and it leads to higher average response times.

There is two query types that causes most of CPU usage, it's count.estimate and select jsonb,id from circulation_storage.requests.

Results

Test 1

Brief overview of resource usage below:

Service CPU usage:

As you can see, there's only one module that uses around 250% CPU usage - it's okapi.

Service Memory usage:

There's no visible memory usage for all relevant modules.

RDS CPU usage:

As you can see above, CPU usage on 50% rate was made by count estimate queries that takes 1.14 seconds in average.

Test 2

Service CPU usage:

Most used modules: 

• OKAPI - 415%;
• Mod-Inventory storage - 73%-75%;
• Mod-users - 60-70
• Mod-circulation - 60-70
• Mod circulation storage - 40;

Services memory usage ;

RDS CPU usage

there is high CPU utilisation from DB side during test. Perhaps select  mentioned on screen above may be optimised to reduce this. because this select taking most of CPU time.  

RDS wait is 1.85 seconds in average;

Test 3

Service CPU usage:

• Okapi- 440 -450;
• Users - 100-115
• Mod inventory storage 101 - 110;
• Circulation - 60-80;
• Circulation storage 40-50

Memory usage:

There is still no visible memory impact on all relevant modules

RDS wait is 2.80 seconds wait;

Test 4

Service CPU usage:

• OKAPI - 400%-500%
• Users 110%-130%
• inventory storage - 95%-125%
• circulation 75% -100%
• Circulation storage 40%-50%

Service memory usage

There is no visible memory impact on all relevant modules