Overview

• This document summarizes the results of edge-patron API testing with different parameters and its values in edge-patron service and mod-circulation service. There're just two requests:

  • GET /patron/account/{id}?includeLoans=true&includeCharges=true&includeHolds=true&apiKey=<API_KEY>  This one retrieves data by user id

  • POST /patron/account/{id}/instance/{instanceId}/hold This one creates requests for the item by instance id for the specified user id

• Tests carried out in Sunflower release on a non-ecs environment ( secp1 in our case, central tenant - fs09000000).

• Jira PERF-1165: edge-patron - Sunflower Parameters TestingClosedPreview

Summary

• All tests completed successfully. Tested API requests with default values perform almost on the same level if to compare with different combinations of parameters except of test #5 with 30 milliseconds improvement where null_keycloak_key_cache_ttl_ms parameter was 15000. 

• GET /patron/account/{id}

  • Best performance: Test #4 (136.02 ms, -8.62 ms vs baseline).

  • Most regression: Test #7 (161.30 ms, +16.66 ms vs baseline).

• POST /patron/account/{externalSystemId}/instance/{instanceId}/hold

  • Best performance: Test #5 (442.29 ms, -31.04 ms vs baseline).

  • Most regression: Test #8 (512.99 ms, +39.66 ms vs baseline).

• Memory consumption for all modules shows a stable trend. No memory leaks are suspected. Edge-patron service used 30% of memory during all tests.

• Service CPU utilization corresponded to the load and almost didn't grow during tests due to small load.

• DB CPU utilization grew from 8% to 14% mostly. Some spikes up to 18% happened.

• Additional retesting of test #6 was performed to see how not warmed up environment can affect the results. There's a possibility of additional latency 50-100 milliseconds if to measure performance without warming up.

Test runs

Test Results

The deltas are not significant to take into account. 

Resource utilization

Service CPU Utilization

Open

Open

Average CPU utilization during the tests

Service Memory Utilization

Memory usage was on level 30% for edge-patron service during all tests

Open

Open

DB CPU Utilization

DB CPU spiked to 18% maximum for all tests

Open

Open

DB Connections

DB connections were 1330 during all tests

DB load

Tests baseline - #5

Open

Open

Tests #6 - #12

Open

Open

Appendix

Infrastructure

PTF - environment Sunflower (secp1)

• 14  r7g.2xlarge EC2 instances located in US East (N. Virginia)us-east-1

• 1 database  instance, writer

  • Name: db.r6g.xlarge

  • Memory GIB: 32 GB

  • vCPUs: 4 vCPUs

• MSK fse-test

  • 4 kafka.m7g.xlarge brokers in 2 zones

  • Apache Kafka version 3.7.x

  • EBS storage volume per broker 300 GiB

  • auto.create.topics.enable=true

  • log.retention.minutes=480

  • default.replication.factor=2