Skip to end of banner
Go to start of banner

Data Import test report (Quesnelia)[non-ECS]

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Overview

This document contains the results of testing Data Import for MARC Bibliographic records at Quesnelia release [non-ECS]. https://folio-org.atlassian.net/jira/people/712020:c7153665-e98d-4df6-a9f4-fe368ae2480f/boards/224?selectedIssue=PERF-836 on QCP1 environment.

Summary

  • All Data-imports jobs finished successfully.

  • Duration for DI increases correlates to the number of the records imported. 

  • The average CPU utilization of modules for all Create and Update jobs did not exceed 150 %. Spikes at the beginning on mod-data-import module are expected because of large file uploading.

  • No memory leak is suspected for DI modules. During DI of 500K on both profiles mod-pubsub has a sawtooth-like memory usage within the range of 40-60%.

  • Approximate DB CPU usage is close to 95% and this number goes for all jobs with files more than 10k records. 

Comparison with previous testing results Data Import test report (Poppy)

  • Duration for Data-import with PTF - Create 2 has not increased significantly. In Quesnelia release there were some changes in the update profile so the new one was created PTF - Updates Success - 6, these durations will be the baseline for the next tests.

  • Services CPU utilization, Service memory utilization, and DB CPU utilization have the same utilization trend and values as in the Poppy release.

Recommendations and Jiras

  1. Investigate data-import job details failed to load MODDATAIMP-1044 - Getting issue details... STATUS

Results

Test #

Data-import test

Profile

Duration

Poppy 

Duration

Quesnelia

Difference, sec

Results

1.

1k MARC BIB Create

PTF - Create 2

39 sec

54 sec

↓ 15 sec

Completed

2.

5k MARC BIB Create

PTF - Create 2

2 min 22 sec

3 min 20 sec

↓ 58 sec

Completed

3.

10k MARC BIB Create

PTF - Create 2

4 min 29 sec

6 minutes

↓ 1 min 31 sec

Completed

4.

25k MARC BIB Create

PTF - Create 2

10 min 38 sec

13 min 41 sec

↓ 3 min 3 sec

Completed 

5.

50k MARC BIB Create

PTF - Create 2

20 min 26 sec

21 min 59 sec

↓ 1 min 33 sec

Completed 

6.

100k MARC BIB Create

PTF - Create 2

2 hours 46 min

Cancelled

40 min 16 sec

Not applicable

Completed

7.

500k MARC BIB Create

PTF - Create 2

Not tested

3 hours 27 min

Not applicable

Completed

8.

1k MARC BIB Update

PTF - Updates Success - 6

34 sec

(PTF - Updates Success - 1)

1 min 59 sec

Not applicable

Completed

9

2k MARC BIB Update

PTF - Updates Success - 6

1 min 09 sec (PTF - Updates Success - 1)

2 min 43 sec

Not applicable

Completed

10

5k MARC BIB Update

PTF - Updates Success - 6

2 min 31 sec (PTF - Updates Success - 1)

7 min 10 sec

Not applicable

Completed

11

10k MARC BIB Update

PTF - Updates Success - 6

5 min 13 sec (PTF - Updates Success - 1)

10 min 27 sec

Not applicable

Completed

12

25k MARC BIB Update

PTF - Updates Success - 6

12 min 27 sec (PTF - Updates Success - 1)

23 min 16 sec

Not applicable

Completed

13

50k MARC BIB Update

PTF - Updates Success - 6

Not tested

40 min 52 sec

Not applicable

Completed

14

100k MARC BIB Update

PTF - Updates Success - 6

Not tested

1 hrs 2 min

Not applicable

Completed

15

500k MARC BIB Update

PTF - Updates Success - 6

Not tested

5 hrs 31 min

Not applicable

Completed

Test Runs 

MARC BIB CREATE

Tests #1-7 1k, 5k, 10k, 25k, 50k, 100k, 500k records

Data-import (Create)

start time

end time

1

500k_bib_Create.mrc

2024-04-01 09:56:59.095+00

2024-04-01 13:26:19.429+00

2

100k_bib_Create.mrc

2024-04-01 09:03:56.04+00

2024-04-01 09:44:12.654+00

3

50k_bib_Create.mrc

2024-04-01 08:18:58.078+00

2024-04-01 08:40:56.215+00

4

25k_bib_Create.mrc

2024-04-01 07:58:48.679+00

2024-04-01 08:12:30.555+00

5

10k_bib_Create.mrc

2024-04-01 07:47:09.388+00

2024-04-01 07:53:08.405+00

6

5k_bib_Create.mrc

2024-04-01 07:40:32.282+00

2024-04-01 07:43:52.674+00

7

1k_bib_Create.mrc

2024-04-01 07:38:30.511+00

2024-04-01 07:39:24.804+00

MARC BIB UPDATE

Tests #8-15 1k, 2k, 5k, 10k, 25k, 50k, 100k, 500k records

Data-import (Update)

start time

end time

1

DI_500K.mrc

2024-04-08 10:55:52.476+00

2024-04-08 16:27:37.544+00

2

DI_100K.mrc

2024-04-08 09:44:16.428+00

2024-04-08 10:46:45.049+00

3

DI_50K.mrc

2024-04-08 08:55:22.263+00

2024-04-08 09:36:15.233+00

4

DI_25K.mrc

2024-04-08 08:24:13.083+00

2024-04-08 08:47:29.199+00

5

DI_10K.mrc

2024-04-08 08:10:05.748+00

2024-04-08 08:20:33.03+00

6

DI_5K.mrc

2024-04-08 08:01:35.162+00

2024-04-08 08:08:45.756+00

7

DI_2K.mrc

2024-04-08 07:56:12.21+00

2024-04-08 07:58:56.049+00

8

DI_1K.mrc

2024-04-08 07:47:59.217+00

2024-04-08 07:49:58.516+00

Service CPU Utilization 

MARC BIB CREATE

Tests #1-7

1k, 5k, 10k, 25k, 50k, 100k, 500k records

CPU utilization for all modules returned by default numbers after all tests. Average for mod-inventory-b - 130%, mod-inventory-storage-b - 25%, mod-source-record-storage-b - 40%, mod-source-record-manager-b - 35%, mod-di-converter-storage-b - 70%, , mod-data-import - 350% spike for 500k job(same behaviour on Poppy version).

image-20240402-125027.png

MARC BIB UPDATE

Tests #8-15

1k, 2k, 5k, 10k, 25k, 50k, 100k, 500k records

image-20240409-093250.png

Memory Utilization

No memory leak is suspected for DI modules.

MARC BIB CREATE

Tests #1-7

1k, 5k, 10k, 25k, 50k, 100k, 500k records

image-20240402-123807.png

MARC BIB UPDATE

Tests #8-15

1k, 2k, 5k, 10k, 25k, 50k, 100k, 500k records

image-20240409-093441.png

RDS CPU Utilization 

MARC BIB CREATE

Average 95% for DI jobs with more than 10k records for Create and Update profiles

image-20240402-125315.png

MARC BIB UPDATE

image-20240409-093522.png

RDS Database Connections

MARC BIB CREATE
When the SUT Data-Import job Create profile typically uses an average of 675 connections, whereas for Update profile, it uses around 640 connections. When the SAR number of the DB connection is about 500.

image-20240402-125422.png

MARC BIB Update

image-20240409-093609.png

Average active sessions (AAS)

MARC BIB CREATE

image-20240402-125550.png

Top SQL

image-20240402-125636.png

MARC BIB UPDATE

image-20240409-095345.png

Top SQL

image-20240409-095508.png

MSK CPU utilization (Percent) OpenSearch

Avarage CPU Utilization is about 9%

image-20240402-130225.png

CPU (User) usage by broker

MARC BIB Create

image-20240402-130345.png

MARC BIB Update

The use of resources on Kafka clusters will not be valid, since testing was carried out on another environment, as well as one connected to the tenant cluster.

Errors

Appendix

Infrastructure

PTF -environment qcp1

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

  • 2 database  instances, writer/reader

    NameMemory GIBvCPUsmax_connections

    db.r6g.xlarge

    32 GiB4 vCPUs2731

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

Module

Task Def. Revision

Module Version

Task Count

Mem Hard Limit

Mem Soft limit

CPU units

Xmx

MetaspaceSize

MaxMetaspaceSize

R/W split enabled

qcp1-pvt

mod-data-import

5

mod-data-import:3.1.0-SNAPSHOT.174

1

2048

1844

256

1292

384

512

FALSE

mod-search

2

mod-search:3.2.0-SNAPSHOT.199

2

2592

2480

2048

1440

512

1024

FALSE

mod-configuration

2

mod-configuration:5.11.0-SNAPSHOT.348

2

1024

896

128

768

88

128

FALSE

mod-permissions

4

mod-permissions:6.5.0-SNAPSHOT.374

2

1684

1544

512

1024

384

512

FALSE

mod-inventory-storage

2

mod-inventory-storage:27.1.0-SNAPSHOT.719

2

4096

3690

2048

3076

384

512

FALSE

mod-source-record-manager

2

mod-source-record-manager:3.8.0-SNAPSHOT.306

2

5600

5000

2048

3500

384

512

FALSE

okapi-b

2

okapi:5.1.2

3

1684

1440

1024

922

384

512

FALSE

Methodology

  1. Pregenerated files were used for DI Create job profile

    • 1K, 2K, 5K, 10K, 25K, 50K, 100K and 500K files.

  2. Run DI Create on a single tenant one by one with the delay with files using PTF - Create 2 profile.

  3. Prepare files for DI Update with the Data export app, using previous imported items

  4. Run DI Update on a single tenant one by one with delay with prepared files using PTF - Update Success 6 profile

  • 1K, 2K, 5K, 10K, 25K, 50K, 100K and 500K files.

  1. Data-import durations were obtained from DB using SQL query

SELECT (completed_date-started_date) as duration, *
	FROM fs09000000_mod_source_record_manager.job_execution
where subordination_type = 'COMPOSITE_PARENT'
order by started_date desc
limit 10
  • No labels