PERF-169 - Getting issue details... STATUS

Overview

In this workflow, we are checking the performance of RMB 32 / Vert.x 4.0.0 with mod-configuration for the Honeysuckle release.

We tested it with 5, 8 virtual users for 30 minutes.

Backend:

mod-users-17.1.0
mod-users-bl-6.0.0
mod-authtoken-2.5.1
mod-permissions-5.11.2
mod-configuration-5.5.0
mod-configuration-5.6.0
okapi-4.3.3

Environment:

63 back-end modules deployed in 110 ECS services
3 okapi ECS services
8 m5.large EC2 instances
2 (1 reader, 1 writer) db.r5.xlarge AWS RDS instance
INFO logging level

High Level Summary

GET by id is ~43% faster
POST is ~40% faster
DELETE is ~43% faster

Test Runs

Test	Virtual Users	Duration
1.	5	30 min
2.	8	30 min

Results

mod-configuration-5.5.0

API	5 Users Average	8 Users Average
GET_/configurations/entries/configId	44 ms	59 ms
POST_/configurations/entries	47 ms	63 ms
DELETE_/configurations/entries/configId	46 ms	61 ms

mod-configuration-5.6.0 - RMB 32 / Vert.x 4.0.0

API	5 Users Average	8 Users Average
GET_/configurations/entries/configId	25 ms	25 ms
POST_/configurations/entries	28 ms	28 ms
DELETE_/configurations/entries/configId	26 ms	26 ms

Database CPU Utilization

The database CPU utilization is around 9%-10% for both releases. mod-configuration-5.6.0 consumes less CPU for 5 Users compared to mod-configuration-5.5.0

mod-configuration-5.5.0

mod-configuration-5.6.0

Service CPU Utilization

For 2 users, max CPU utilization increases and then stabilizes as the number of loans increases. Therefore, CPU utilization is relatively on the lower side.

mod-configuration-5.5.0

mod-configuration-5.6.0

Service Memory Utilization

Service memory was stable for most modules except mod-circulation which was on the higher side. For service with the highest Memory utilization is shown by range to get a better picture.