Table of Contents

...

The test's target is to investigate the behaviour of the Check-In/Check-Out activities during fixed load tests.

Summary

...

Check-In/Check-Out tests on Quesnelia release (Eureka) in QECP1 environment carried out with 8, 20, 30, 75 virtual users during 45 minutes and with 30 virtual users during longevity test (24 hours) to detect any trends in resource utilization

...

• RDS CPU utilization average
  • For both 45 minute and longevity tests RDS used max 867 connections. Without test it was 812 connections.

• CPU (User) usage by broker
  • Common CPU utilization by broker during longevity was 18, 18, 16, 14% accordingly to broker distribution. Resource utilization decreased significantly after 6 hours 20 minutes (17:40 UTC) to 14, 12, 12, 11%

Notes:

• The reason of degradation, which occurs after 6 hours of testing, has not yet been found.

Recommendations

• Investigate degradation after 6 hours of longevity test.

Test Runs 

The following table contains  tests configuration information

Results

...

Response time

The table contains results of Check-in, Check-out tests in Quesnelia release (Eureka). All requests that are >= 100 ms (in average response times)

...

During the test RDS grew from 32% to 40% in average. Spikes observed after 10 hours

RDS Database Connections

For both 45 minute and longevity tests RDS used max 867 connections. Without test it was 812 connections.

45 minute tests

Longevity test

CPU (User) usage by broker

Common CPU utilization by broker during all tests was 18, 15, 15, 13 % accordingly to broker distribution in 45 min tests

Common CPU utilization by broker during longevity was 18, 18, 16, 14% accordingly to broker distribution. Resource utilization decreased significantly after 6 hours 20 minutes (17:40 UTC) to 14, 12, 12, 11%

45 minute tests

Longevity test

Longevity

Target Group 5XX Count

...