| Table of Contents |
|---|
Overview
This is initial report for EBSCONET orders renewal workflow testing
. The purpose of this document is to highlight KPIs of EBSCONET workflow, find possible bottlenecks/ issues, and define the baseline performance for this workflow since it hasn't been tested before. EBSCONet is a client application that calls edge-orders to renew orders. The tests simulate EBSCONet calling edge-orders by issuing calls to retrieve a Purchase Order Line (POL) and updating it with relevant information for renewal.Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key PERF-285
...
No memory leaks were found.
High level results:
| Test # | VUsers | Duration | response time (get) ms. | response time (put) ms | Error rate | ||||
| avg | 75% | 95% | avg | 75% | 95% | ||||
|---|---|---|---|---|---|---|---|---|---|
| 1 | 2 | 7 min 10 s | 249 | 257 | 287 | 178 | 184 | 197 | 2.6% (52 calls) |
| 2 | 2 | 7 min | 247 | 254 | 288 | 178 | 184 | 197 | 3.3% (67 calls) |
| 3 | 10 | 4 min 30 s | 298 | 319 | 404 | 236 | 253 | 339 | 1.14% (57 calls) |
| 4 | 10 | 4 min 10 s | 308 | 332 | 417 | 242 | 263 | 465 | 1.56% (78 calls) |
Recommendations & Jiras
Jira Legacy server System
...
Ticket to handle NullPointerException Which is reproducible even with 2 users.JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODEBSNET-56 Jira Legacy server System
...
Ticket to handle internal server error .JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODEBSNET-57 - We have noticed that mod-orders-storage has allocated only 128 CPU units. It's better to increase CPU units value of mod-orders-storage based on CPU utilization (at least 3x times)
Test Runs
Test # | VUsers | Data set | Load generator size | Load generator Memory(GiB) |
| 2 users |
| t3.medium | 3 |
| 2. normal conditions | 2 users |
| t3.medium | 3 |
3. extreme conditions | 10 users |
| t3.medium | 3 |
| 4 extreme conditions | 10 users |
| t3.medium | 3 |
Results
| Test # | VUsers | Duration | response time (get) ms. | response time (put) ms | Error rate | ||||
| avg | 75% | 95% | avg | 75% | 95% | ||||
|---|---|---|---|---|---|---|---|---|---|
| 1 | 2 | 7 min 10 s | 249 | 257 | 287 | 178 | 184 | 197 | 2.6% (52 calls) |
| 2 | 2 | 7 min | 247 | 254 | 288 | 178 | 184 | 197 | 3.3% (67 calls) |
| 3 | 10 | 4 min 30 s | 298 | 319 | 404 | 236 | 253 | 339 | 1.14% (57 calls) |
| 4 | 10 | 4 min 10 s | 308 | 332 | 417 | 242 | 263 | 465 | 1.56% (78 calls) |
...
PTF -environment ncp3-pvt
- 9 m6i.2xlarge EC2 instances located in US East (N. Virginia)us-east-1
- 2 instances of db.r6.xlarge database instances, one reader, and one writer
- MSK ptf-kakfa-3
- 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
...