Data Import with Check-ins Check-outs Nolana

Infrastructure

PTF -environment ncp3

  • 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


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.11-221024

2208

(1872 in MG)

1952

(1684 in MG)

512m1440m
okapi4.14.71-231024

1684

(1512 in MG)

1440

(1360 in MG)

512m922m
mod-feesfines18.1.01-221281024896128768
mod-patron-blocks1.7.11-2210241024896128768
mod-pubsub2.7.01-221024

1536

(1440 in MG)

1440

(1296 in MG)

512922
mod-authtoken2.12.01-22

512

(128 in MG)

1440

(1024 in MG)

1152

(896 in MG)

128

922

(768 in MG)

mod-circulation-storage15.0.01-221024

1536

(1152 in MG)

1440

(1024 in MG)

512896
mod-circulation23.3.01210241024896128768
mod-configuration5.9.01-221281024896128m768m
mod-users19.0.01-222581024896128m768m
mod-remote-storage1.7.01-2212818721684512m1178m
mod-data-import-cs1.15.11-222581024896128m768m
mod-quick-marc2.5.01-21128

2288

(2098 in MG)

2176

(1920 in MG)

512m1664m
mod-source-record-storage5.5.21-221024

1536

(1440 in MG)

1440

(1296 in MG)

512m908m
mod-data-import2.6.11-2125620481844512m1292m
mod-source-record-manager3.5.42-321024

4096

(2048 in MG)

3688

(1844 in MG)

512m

(800M in MG)

2048m

(1024m in MG)

MG- Morning Glory release

Front End:

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

Summary 

  • In Nolana, there is a significant improvement in the performance of data import and CheckIn/CheckOut compared to KIWI and Lotus.
  • The time of Data Import with CI/CO is even better than without CI/CO. Apparently, the reason is for the baseline test the mod-source-record-manager version was 3.5.0 for the test with CI/CO it was 3.5.4.
  • From time to time there are spikes in response time for CI/CO up to 10 seconds.
  • RDS CPU Utilization was high up to 97%

Results


MARC FileProfileDI DurationCheck In (CI), Check Out (CO)



usersCI Average (seconds)CO Average (seconds)
5K.mrcPTF - Create 200:01:56.84780.8171.417
10K.mrcPTF - Create 200:03:57.45580.8421.574
25K.mrcPTF - Create 200:09:24.24980.8821.641
50K.mrcPTF - Create 200:19:28.93380.9261.666
100K.mrcPTF - Create 200:38:44.75181.0211.862
5K.mrcPTF - Updates Success - 100:02:51.52580.7471.094
10K.mrcPTF - Updates Success - 100:04:57.680.5411.026
25K.mrcPTF - Updates Success - 100:13:12.5380.7001.248
50K.mrcPTF - Updates Success - 100:27:39.69380.7001.199
100K.mrcPTF - Updates Success - 100:48:45.33580.5561.046

Bolded numbers are the best response time of CI/CO and the smallest spikes of response time. For  10k MARC Update response time of CI/CO with data import is even better than for CI/CO with 5k MARC Update. For 100k.mrc response time is almost the same as for 10k.mrc that's why it is 2 sets of bolded numbers here.

Comparisons

The following table compares additional test results to previous release numbers and to the CICO baselines Nolana (of Check In average time 0.456s and Checkout average time 0.698s). Note that Lotus numbers are in red, Nolana numbers are in black, and Kiwi numbers are in blue.

In the Nolana version, there is a significant improvement in the performance of data import and CheckIn/CheckOut.

For the baseline test the mod-source-record-manager version was 3.5.0 for the test with CI/CO it was 3.5.4. Apparently, it is the reason why the time of Data Import with CI/CO is even better than without CI/CO.


Profile

Duration

KIWI (Lotus) without CICO

Duration

with CICO 8 users KIWI (Lotus)

Duration

Nolana without CICO

Duration

with CICO 8 users Nolana

CheckIn average (seconds) 

CheckOut average (seconds) 

Deviation From the baseline CICO response times

5K MARC BIB Create

PTF - Create 2

5 min, 8 min (05:32.264)

(08:48.556)

 5 min

(05:48.671)

2 min 51 s00:01:56.847

0.851

0.817

1.388

1.417

CI:  44%

CO:  51%

5K MARC BIB Update

PTF - Updates Success - 1

11 min, 13 min

(10:07.723)

7 min

06:27.143

2 min 27s00:02:51.525

1.102

0.747

1.867

1.094

CI:  39%

CO:  36

10K MARC BIB Create

PTF - Create 2

11 min , 14 min

10:07.723

 13 min

00:10:47.622

4 min 55 s00:03:57.455

1.354

0.842

2.271

1.574

CI:  46%

CO: 56%

10K MARC BIB UpdatePTF - Updates Success - 1

22 min, 24 min


15 min

20:46.29

4 min 50 s00:04:57.6

0.864

0.541

1.655

1.026

CI:  16%

CO: 32%

25K MARC BIB CreatePTF - Create 223 mins, 25 mins, 26 mins

31 min

32:21.273

11 min 56 s00:09:24.249

1.248

0.882

2.078

1.641

CI:   48%

CO: 57%

25K MARC BIB UpdatePTF - Updates Success - 127 min, 40 mins, 56mins

33 min

31:40.429

12 min 20 s00:13:12.53

0.951

0.700

1.658

1.248

CI:  35%

CO: 44%

50K MARC BIB CreatePTF - Create 2

40 mins, 43mins

49:55.86

63 min

47:53.93

23 min 43 s00:19:28.933

1.271

0.926

2.095

1.666

CI:   51%

CO:  58%

50K MARC BIB UpdatePTF - Updates Success - 1

64 min

48:46.35

FAILED


24 min 5 s00:27:39.693

-

0.700

-

1.199

CI:  35%

CO: 42%

100K MARC BIB CreatePTF - Create 2--49 min 40 s00:38:44.751

-

1.021

-

1.862

CI:  55%

CO: 63%

100K MARC BIB UpdatePTF - Updates Success - 1--51 min 15 s00:48:45.335

-

0.556

-

1.046

CI:  18%

CO: 33%

Response Time Comparison Graph

MARC BIB Create

MARC BIB Update 

Memory Utilization

MARC BIB Create

MARC BIB Update

CPU Utilization

MARC BIB Create


MARC BIB Update

RDS CPU Utilization

MARC BIB Create

MARC BIB Update