GET /accounts test report


PERF-147 - Getting issue details... STATUS




PERF-147 - Getting issue details... STATUS

Overview

The purpose of this test is to compare results from two identical test runs on Goldenrod and Honeysuckle environments, and to find the reason of slowness if any will be there. 

Summary

In this particular case BHS1 (Honeysuckle) is faster than GCP1 (Goldenrod). BHS1 is even more stable than GCP1 as we saw mod feesfines in GCP1 failed 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

Tests

Test#Virtual UsersDurationEnvComment
1101800BHS1-
2101800GCP1-
3101800BHS1All relevant modules restarted*
4101800GCP1All relevant modules restarted*
  • mod-inventory-storage, mod-feesfines, okapi.


Results comparison

Test#EnvRequests


Response times (Seconds)
TotalKOReq/s50th pct75th pct95th pct
1BHS1GET /accounts?query=loanId==(loanUUID or loanUUID)&limit=2147483647133815074.3390.1120.1360.214
2GCP144932337224.9590.4140.4670.560
3BHS1138052076.6930.1110.1380.243
4GCP142342023.5210.4190.4680.553

Test#1

Service CPU usage for relevant modules


Service memory usage for relevant modules


DB RDS 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"


DB RDS CPU usage 

Query that takes most of time:

Test#3

Service CPU usage for relevant modules

Service memory usage for relevant modules:

DB RDS CPU usage

Test#4

Service CPU usage for relevant modules


Service memory usage for relevant modules


DB RDS CPU usage