Overview

This is a report for a series of Check-in-check-out test runs against the Honeysuckle release. PERF-135 - Getting issue details... STATUS

Backend:

• mod-circulation-19.2.7
• mod-circulation-storage-12.1.4
• mod-inventory-16.1.3
• mod-inventory-storage-19.4.4
• mod-authtoken-2.6.0
• mod-pubsub-1.3.3
• okapi-4.3.3 (also with 4.2.2)

Frontend:

• folio_circulation-4.0.1
• Item Check-in (folio_checkin-4.0.1)
• Item Check-out (folio_checkout-5.0.1)

Environment:

• 61 back-end modules deployed in 110 ECS services
• 3 okapi ECS services
• 8 m5.large  EC2 instances
• 2 db.r5.xlarge AWS RDS instance
• INFO logging level

High Level Summary

• Check-out: Honeysuckle is slower by 9%-28% than Goldenrod
• Check-in: 4%-22% slower than Goldenrod
• APIs turned slower in Honeysuckle: GET /automated-patron-blocks/{id} (150% slower) and  GET /circulation/loans (60%). These are covered by MODPATBLK-70 and CIRC-1014, respectively
• Okapi v4.3.3 seem to be using 2x-3x CPU cycles than in v1.3.2 (Goldenrod).  Potential issue found with the logging methods OKAPI-964 
• mod-pubsub has a memory leak that would drag down performance under high loads (see section on longevity test): MODPUBSUB-136
• Caching Okapi tokens in Okapi reduced mod-authtoken's CPU usage by over 90%
• Database's memory usage improved dramatically from Goldenrod's - little memory consumptions observed.

Test Runs

Results

Response Times

The following table shows the slow 75th percentile APIs taking more than 100 ms to return, and also comparing them against Goldenrod's.  Other than the 1-user test, starting with the 5-users test, all listed APIs are slower with GET automated-patron-blocks leading the way at 150% slower, while GET circulation/loans regressed up to 60%

Note: GR = Goldenrod build, HS = Honeysuckle build