How fast, will it last

Overview

This section details the process used to conduct the performance tests of the platform.

The tests aimed to find the following answers:

• What is the performance limit of the system given the available resources?
• Does the system maintain stability over a longer period?
• How does the system handle a temporary spike in traffic?

Following business scenarios were tested:

• Activation and modification of a convergent mobile + fixed service - 60%/40% blend.
• Activation of a mobile service.

Traffic patterns:

• Short term heavy load profile
• Long term medium load profile

Environment

The tests were conducted in two environments:

Amazon Web Services

AWS EKS Cluster + Atlas MongoDB

• EKS (opens in a new tab) K8s cluster (resource quota: cpu 34, memory 65 Gi)
• 5 x t3.xlarge (opens in a new tab) nodes
• 1 x Atlas MongoDB M30 (2 x vCPU, 8 GB RAM)

On prem

Client's on prem environment: K8s cluster on premise + MongoDB on prem

• K8s cluster (resource quota: cpu 30, memory 60 Gi)
• MongoDB (4 x vCPU, 24 GB RAM)

We thank our Client for allowing us to publish the test results conducted

Results

On the mentioned on prem environment, the following results were achived:

• Up to 210 convergent orders/minute stable load conditions in the 60%/40% blend.
• Up to 600 convergent orders/minute, peak periods in the blend.
• Up to 700 mobile orders/minute, peak periods.

The system remained stable, with peak traffic correctly queued and processed shortly after the test concluded

We stopped furter testing as we lost hope in finding the limit ;-)

Meat & Bones

Blended traffic, 1 hour

Within these test scenarios, the system was loaded with orders over the course of 1 hour. 60% of these orders were activation orders for the converged service (mobile + fixed), while 40% were orders modifying the converged service.

Mobile orders only, 1 hour

Within this test scenario, the system was loaded with orders during 1 hour. 100% of the orders were activation orders for mobile service.

Blended traffic, 6/12 hours

During these test scenarios, the system was loaded with orders over the course of 1 hour, while 60% of these orders were activation orders for the converged service (mobile + fixed line) and 40% ot them modifying the converged service.