Combined Bulk edit + Check-in-check-out Test Report (Nolana)

20-users testsAvgMax

mod-users21%21%

mod-pubsub5%5%

okapi14%14%

mod-circulation4%4%

mod-circulation-storage5%5%

mod-inventory7%7%

mod-inventory-storage7%7%

mod-patron-blocks1%1%

mod-feesfines17%17%

mod-authtoken31%20-users testsAvgMax


mod-users21%21%


mod-pubsub5%5%


okapi14%14%


mod-circulation4%4%


mod-circulation-storage5%5%


mod-inventory7%7%


mod-inventory-storage7%7%


mod-patron-blocks1%1%


mod-feesfines17%17%


mod-authtoken31%78%














Overview

This is a report for a series of Check-in-check-out test runs together with Bulk edits against the Nolana release. 

Infrastructure

PTF -environment ncp3

  • 10 m6i.2xlarge EC2 instances located in US West (Oregon)us-west-2 AWS region (comparing to 10 m6i.2xlarge EC2 instances located in US East (N. Virginia)us-east-1 for Morning Glory release)
  • 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=truec
    • log.retention.minutes=480
    • default.replication.factor=3

Modules memory and CPU parameters

Modules

Version

Task Definition

Running Tasks 

CPU

Memory

MemoryReservation

MaxMetaspaceSize

Xmx

mod-inventory19.0.112102428802592512m1814m

mod-inventory-storage

25.0.1121024

2208

(1872 in MG)

1952

(1684 in MG)

512m1440m
okapi4.14.7131024

1684

(1512 in MG)

1440

(1360 in MG)

512m922m
mod-feesfines18.1.0121281024896128768
mod-patron-blocks1.7.11210241024896128768
mod-pubsub2.7.0121024

1536

(1440 in MG)

1440

(1296 in MG)

512922
mod-authtoken2.12.012

512

(128 in MG)

1440

(1024 in MG)

1152

(896 in MG)

128

922

(768 in MG)

mod-circulation-storage15.0.0121024

1536

(1152 in MG)

1440

(1024 in MG)

512896
mod-circulation23.3.01210241024896128768

MG- Morning Glory release

Front End:

  • Item Check-in (folio_checkin-7.2.0)
  • Item Check-out (folio_checkout-8.2.0)

High-Level Summary

  • In general, there are insignificant regressions in performance for Check-in and check-out during bulk editing. Bulk edit duration is shorter than without CI/CO.
  • Memory usage is stable for all modules, except for mod-data-export-workerincreased from 57% to 60% (Stable CPU utilization was after reaching 98% in Morning Glory).
  • The relevant services overall seem to occupy CPU resources nominally. Only mod-authtoken seems to have the spikes but the processes did not crash. CPU usage of all modules did not exceed 41%, except for mod-users up to 75%.
  • RDS CPU utilization did not exceed 41%.

Test Runs

Test

Virtual Users

Duration of CI/CO

Load generator size (recommended)Load generator Memory(GiB) (recommended)

1.

8 users CI/CO + Items editing30 minst3.medium3

2.

8 users CI/CO + Users editing10 minst3.medium3

3.

8 users CI/CO + Holdings editing10 minst3.medium3
4.8 users CI/CO+ Items, Users & Holdings editing30 minst3.medium3

Results

Response Times (Average of all tests listed above, in seconds)


Check-in-check-outBulk edit

Average (seconds)50th %tile (seconds)75th %tile (seconds)95th %tile  (seconds)ItemsUsersHoldings

Check-inCheck-outCheck-inCheck-outCheck-inCheck-outCheck-inCheck-out10k records2500 records10k records
Test 10.4310.7930.4170.7700.4440.8070.5040.93020 min--
Test 20.4510.8050.4280.7670.4560.8070.5801.001-1 min-
Test 30.4280.7900.4100.7610.4340.7950.5210.923--11 min 20 sec
Test 40.4360.7970.4260.7760.4500.8110.5040.94129 min1 min11min 20 sec
CI/CO 8 users to compare0.4560.6980.4410.6720.4710.7090.5340.839---

Response times are consistently good.

Memory Utilization

  • Memory usage is stable for all modules, except for mod-data-export-workerincreased from 57% to 60% (98% in Morning Glory).


 Modules CPUs Utilization

The relevant services overall seem to occupy CPU resources nominally. Only mod-authtoken seems to have the spikes but the processes did not crash. CPU usage of all modules did not exceed 41%, except for mod-users up to 75%.



Database and network

RDS CPU usage did not exceed 46%