Overview

This is initial report for EBSCONET orders renewal workflow testing

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], 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.

Summary

During testing we've find several issues: 

• NullPointerException
• Internal server error

No memory leaks were found. 

High level results:

Recommendations & Jiras

• Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODEBSNET-56

   Ticket to handle NullPointerException Which is reproducible even with 2 users.

• Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODEBSNET-57

  Ticket to handle internal server error .
• 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 

Results

Memory Utilization

CPU Utilization 

Most used module - mod-orders-storage. During tests with 10 users it reaches 320% of CPU usage

RDS CPU Utilization 

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 
  
  • 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

...

Methodology/Approach

According to EBSCONET order renewal integration testing we have designed test containing two calls [get] /orders/order-lines/${polineNumber}?type=EBSCONET&apiKey=${API_KEY}

and [put] /orders/order-lines/${polineNumber}?type=EBSCONET&apiKey=${API_KEY} with payload :

{
    "currency": "USD",
    "fundCode": "NEW2023",
    "poLineNumber": "${polineNumber}",
    "quantity": 1,
    "unitPrice": 1.0,
    "vendor": "ZHONEWAX$%",
    "vendorAccountNumber": "libraryorders@library.tam",
    "vendorReferenceNumbers": [],
    "workflowStatus": "Open"
}

Test data creation

In order to create test data (orders with PO lines) we used SQL script. This script will create orders for particular organization ()

...