Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
Overview

This document contains the results of testing different configurations of modules  with changes in JAVA_OPTS replacing XMX with MaxRAMPercentage. Memory utilization, The main KPI for these tests are Memory consumption of modules, Data import durations and Check-in / Check-out response times and Data Import durations for MARC Bibliographic records should be compared.

Ticket:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyPERF-893

...

Test Runs 

Test #

Scenario

Load levelJAVA_OPTS
120 vUsers longevity CI/CO + DI MARC Bib Create12 Data Import tests with 100K sequentially (with 5 min pause)
-XMX
220 vUsers longevity CI/CO + DI MARC Bib Create12 Data Import tests with 100K sequentially (with 5 min pause)
-XX:MaxRAMPercentage, Default
320 vUsers longevity CI/CO + DI MARC Bib Create12 Data Import tests with 100K sequentially (with 5 min pause)-XX:MaxRAMPercentage, Recommended - 66%

Test Results



Comparison

The following table compares test results 

 BASELINE, XMX   STEP #1 default MaxPercentage 

STEP #2 recommended MaxPercentage, 66%
Baseline 16 hours CICO
hh:mm:ss24 hours CICO
hh:mm:ssdelta, default - xmx x hours CICO
hh:mm:ssdelta, 66% - xmx















DI 100k Create #1101:39:094 jobs stucked
DI 100k Create #11





DI 100k Create #1001:03:19

DI 100k Create #10





DI 100k Create #900:59:40

DI 100k Create #900:56:10

DI 100k Create #800:55:01
DI 100k Create #800:58:4700:03:46
DI 100k Create #800:55:2300:00:22

DI 100k Create #700:54:43
DI 100k Create #700:58:0800:03:26
DI 100k Create #702:46:273 jobs stucked

DI 100k Create #600:55:25
DI 100k Create #600:56:0900:00:44
DI 100k Create #601:03:0700:07:42

DI 100k Create #500:54:45
DI 100k Create #500:58:1900:03:33
DI 100k Create #501:03:3700:08:52

DI 100k Create #400:55:38
DI 100k Create #400:54:2700:01:11
DI 100k Create #400:59:1100:03:33

DI 100k Create #300:53:30
DI 100k Create #300:54:3600:01:06
DI 100k Create #300:58:3400:05:04

DI 100k Create #200:53:16
DI 100k Create #200:53:0300:00:13
DI 100k Create #200:57:5900:04:43

DI 100k Create #100:52:51
DI 100k Create #101:05:1000:12:18
DI 100k Create #101:05:4200:12:50












DI +DI -
DI +DI -


DI +DI -Check-Ins
CI1162538Check-InsCI985467

Check-InsCI9431254469470
Check-OutsCO1840978Check-OutsCO1476809

Check-OutsCO14082135834955


Detailed CICO response time for CICO with DI

...

Infrastructure

PTF -environment pcp1

  • 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

...

  1. Run baseline for Check-in / Check-out longevity test with Data import Create job with 100k file.
  2. Change revisions of modules with needed configuration of JAVA_OPTS - replaced XMX with MaxRAMPercentage in aa
  3. Run CI/CO
  4. Run DI script after ramp-up period for CI/CO or at least 10-15 minutes

...