Overview

This is initial report for EBSCONET workflow testing. The purpose of this document is to highlight KPI of EBSCONET workflow, find possible bottlenecks/ issues. Define baseline

Summary

[ A bulleted-list of the most important and relevant observations from the test results. What are the most important things the readers need to know about this testing effort? Some suggestions

Comparison to previous test or release of response times or API durations
Any notable changes
Particular response time or durations
Service memory and/or CPU utilization
RDS memory and/or CPU utilization
Other interesting observations

]

used modules:

mod-organizations
mod-organizations-storage
mod-finance
mod-finance-storage
nginx-edge
mod-ebsconet
nginx-okapi
mod-orders
mod-orders-storage
okapi
mod-mod-notes
mod-configuration
edge-orders

Recommendations & Jiras (Optional)

[ If there are recommendations for the developers or operations team, or anything worth calling out, list them here. Also include any Jiras created for follow-up work]

Test Runs

Test #	VUsers	Data set	Load generator size	Load generator Memory(GiB)
normal conditions	2 users	Number of order lines being renewed 1000 Number of orders being renewed 804 4 of these orders have 50 POLs each - 800 orders with 1 POL each	t3.medium	3
2. normal conditions	2 users	Number of order lines being renewed 1000 Number of orders being renewed 804 4 of these orders have 50 POLs each - 800 orders with 1 POL each	t3.medium	3
3. extreme conditions	10 users	Number of order lines being renewed 5000 Number of orders being renewed 4804 4 of these orders have 50 POLs each - 4800 orders with 1 POL each	t3.medium	3
4 extreme conditions	10 users	Number of order lines being renewed 5000 Number of orders being renewed 4804 4 of these orders have 50 POLs each - 4800 orders with 1 POL each	t3.medium	3

Results

Test #	VUsers	Duration	Error rate
1	2	7 min 10 s	2.6% (52 calls)
2	2	7 min	3.3% (67 calls)
3	10	4 min 30 s	1.14% (57 calls)
4	10	4 min 10 s	1.56% (78 calls)

Memory Utilization

	Nolana Avg%
mod-organizations	25%
mod-organizations-storage	24%
mod-finance	29%
mod-finance-storage	28%
nginx-edge	2%
mod-ebsconet	37%
nginx-okapi	3%
mod-orders	44%
mod-orders-storage	34%
okapi	36%
mod-notes	43%
mod-configuration	25%
edge-orders	20%

CPU Utilization

[Description of notable observations of modules and instances CPU utilization with screenshots (of all modules and involved modules) and tables]

RDS CPU Utilization

Additional information from module and database logs (Optional)

[ Although it is optional to look at logs it is always recommended to look at the logs to see if there were any errors, exceptions, or warnings. If there were any, create Jiras fo rthe module that generated the warnings/errors/exceptions]

Appendix

Infrastructure

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 [ kafka configurations]
- 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

Modules memory and CPU parameter

Modules	Version	Task Definition	Running Tasks	CPU	Memory	MemoryReservation	MaxMetaspaceSize	Xmx
mod-organizations	1.6.0	2	2	128	1024	896	128	700
mod-organizations-storage	4.4.0	2	2	128	1024	896	128	700
mod-finance	4.6.2	2	2	128	1024	896	128	700
mod-finance-storage	8.3.1	2	2	128	1024	896	128	700
nginx-edge	nginx-edge:2022.03.02	1	2	128	1024	896	N/A	N/A
mod-ebsconet	1.4.0	2	2	128	1024	896	256	700
nginx-okapi	nginx-okapi:2022.03.02	1	2	128	1024	896	N/A	N/A
mod-orders	12.5.4	2	2	1024	2048	1440	256	896
mod-orders-storage	13.4.0	2	2	128	1024	896	128	700
okapi	4.14.7	1	3	1024	1684	1440	922	922
mod-mod-notes	4.0.0	2	2	128	1024	896	128	322
mod-configuration	5.9.0	3	2	128	1024	896	128	768
edge-orders	2.7.0	2	2	128	1024	896	128	700

Methodology/Approach

[ List the high-level methodology that was used to carry out the tests. This is important for complex tests that involve multiple workflows. It's important to inform readers of how the tests were performed so that they can comment on any flaw in the test approach or that they can try to reproduce the test results themselves. For example:

Start CICO test first
Run a Data Import job after waiting for 10 minutes
Run an eHoldings job after another 10 minutes
On another tenant run another DI job after 30 minutes in

The steps don't need to be very specific because the details are usually contained in the participating workflow's README files (on GitHub). However, anything worth calling out that was not mentioned elsewhere should be mentioned here.]

Additional Screenshots of graphs or charts (Optional)

[ Optionally include additional screenshots of graphs on the Cloudwatch and Grafana dashboards for completeness sake. These don't have to be solely included in here but can be added in any section if they complement other graphs and fit the narrative. ]

PTF-EBSCONET Workflow