Introduction

Purpose

The purpose of this stress test plan is to evaluate the performance, stability, and scalability of the Call For Rent process under stress load conditions. The objective is to identify potential bottlenecks, weaknesses, and the maximum capacity of the application before failure or significant performance degradation occurs.

Objectives

• Confirm the flow itself is stable and covers the expected scenarion
• Validate the preliminary detected issue witn Accounting ledger

Environments / Infrastructure

Sergey's primary environmnet (dedicated): https://dev-sergey.life-connect.fr/ui/

Limits:

• memory: 680Mi

Requests:

• cpu: 150m
• memory: 680Mi

Pipeline used for run: FLCS-3362_LifeConnect_handle_CFR

Run paramenets (full cleanup)

Run paramenets (call 1st rent)

Run parameters (call regular rent)

Data Set

Middle size dataset: 500RC per 5 Orgs
Data set location: 1NMXfQeup9GKo7rLTHImqNjObrFJ--N8bmAVFYlCBV4M

Scenari(s)

Provide full cycle of Test flow including:

• Full data cleanup/upload (w/o recording):
  • cleanup all the collections (besides the initial company list)
• Call for 1-st rent (recodring)
• Call for regular rent (recodring)

Collected run reports

The are 2 types of reports colected during the run:

• standard Artillery reports
• JFR (Java Flight Recorder) reports

Raw reports collected during the run are connected to test run itself and stored as bitbacket artifacts: raw report 1, raw report 2

As well as raw reports HTML-based version of Artillery could be view directly for:

• call-rc-first-rent
• call-rc-regular-rent

Summary and conclusions

From the goals perspective run could be considered as failed:

• 1-st call 4 rent cycle was fully processed
• call 4 regular rent cycle was interrupted (server restart) and even havent stored the JFR results

As a next step it was recomended to:

• extend server side resources to be more close to production capacity
• check if the resource extention brings the positive results/dynamics in terms of processed RC amount