| Table of Contents |
|---|
...
- Load tests showed that ListApp refreshing duration is
- 1.5 min for 3 users test (1 user on each of three tenants);
- 2.3 min for 10 users test (3-4 user on each of three tenants).
- Load test for 30 users (10 users per tenant) failed due to DB overload (100% of refresh transactions failed).
- During the 10 users test CPU utilization reached 200% for mod-fqm-manager and 111% for mod-lists. Also, mod-permissions CPU utilization exceeded 100% during 30 users test.
- Maximum DB CPU utilization reached 83% (writer instance) and 99% (reader instance) during 30 user test. . In comparison with testing with R/W split disabled, RDS CPU utilization didn't decrease with R/W split feature enabled.
- Memory utilization for mod-permissions increased from 48% to 76% during the tests. No memory leak is suspected for all the modules.
...
| Transaction | Duration, avg | Release | Tenants | Number of users | R/W split | Other conditions |
|---|---|---|---|---|---|---|
ListApp refresh | 10 min 40 sec | [Orchid] | 1 tenant | 10 users | disabled | |
| 8.5 min | [Poppy] | 1 tenant | 10 users | disabled | ||
| 17.7 min | [Poppy] | 1 tenant | 10 users | disabled | Testing in parallel with DI and CICO | |
| ListApp refresh current test results** | 1.5 min | [Poppy] | 3 tenants | 3 users | enabled | |
| 2.3 min | [Poppy] | 3 tenants | 10 users | enabled | ||
| error | [Poppy] | 3 tenants | 30 users | enabled | 100% of refresh transactions failed |
* Query used in lists - "Item status == Checked out". List refresh result is 200K records. Results are taken from previous test reports: [Poppy] List App + with multiple workflows test report and R/W split disabled test report, [Orchid] List App test report
...
Maximum DB CPU utilization reached 83% (writer instance) and 99% (reader instance) during 30 user test.
In comparison with testing with R/W split disabled, RDS CPU utilization didn't decrease with R/W split feature enabled.
DB Connections
DB Load
Writer DB node
...
Infrastructure
PTF -environment pcp1
- 10 m6i.2xlarge EC2 instances located in US East (N. Virginia)us-east-1
1 database instance, writer
Name API Name Memory GIB vCPUs max_connections R6G Extra Large db.r6g.xlarge 32 GiB 4 vCPUs 2731 - MSK tenant
- 4 m5.2xlarge brokers in 2 zones
Apache Kafka version 2.8.0
EBS storage volume per broker 300 GiB
- auto.create.topics.enable=true
- log.retention.minutes=480
- default.replication.factor=3
...