Skip to end of banner
Go to start of banner

[Poppy] List App + multiple workflows test report

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 20 Next »

Overview

This document contains the results of testing List App refreshing of 200k records with multiple parallel workflows (Check-in/Check-out and Data import) in the Poppy release. The goal of testing is to assess the performance of mod-lists along with other workflows (CICO and DI)  and to measure mod-lists's impact on other modules

Ticket: PERF-691 - Getting issue details... STATUS

Summary

  • ListApp refreshing duration is about 8.5 min when testing separately from other workflows. With Data Import and Check-in/Check-out scenario ListApp duration has +108% increase and reaches 17.7 min. It's above the expected value of 10 minutes.
  • Data Import and Check-in/Check-out response time also increase about 10-20% with ListApp scenario added.
  • According to the results, CPU utilization for DI + CICO test was about 80%, while with ListApp scenario added CPU reached 155%.
  • RDS CPU utilizatoin is about 90% for DI+CICO test and it doesn't increase with ListApp scenario added.

Test runs

ScenarioData quantity
List App* + Check-in/Check-out + Data Import Create**

ListApp - 10 users

CICO - 20 users

DI - 25k

 Check-in/Check-out + Data import**

CICO - 20 users

DI - 25k

List AppListApp - 10 users

*200k records list refresh for each user.

**PTF Create 2 job was used for DI scneario

Results

TransactionDuration

Degradation

[Orchid]

Testing separately

[Poppy]

Testing separately

(ListApp and DI+CICO)

[Poppy]

Testing in parallel

ListApp refresh, avg

from 9 min 40 sec to

10 min 40 sec

8.5 min17.7 min+108%
Check-in, avg
1.173 sec1.290 sec+9.9%
Check-out, avg
1.648 sec1.948 sec+18.2%
DI Create 25k 
18 min22 min+22%

Grafana results

Instance CPU Utilization

ListApp

DI + CICO

ListApp + DI + CICO

Service CPU Utilization

According to the results, CPU utilization for DI + CICO test was about 80%, while with ListApp scenario added CPU reached 155%.

ListApp

DI + CICO

ListApp + DI + CICO

Memory Utilization

No memory leacks were found during the tests.

ListApp

DI + CICO

ListApp + DI + CICO

DB CPU Utilization

RDS CPU utilizatoin is about 90% for DI+CICO test and it doesn't increase with ListApp scenario added.

ListApp

DI + CICO

ListApp + DI + CICO

DB Load

ListApp

DI + CICO

ListApp + DI + CICO


Additional info

Grafana graphs:

List App + Check-in/Check-out + Data Import Create

http://carrier-io.int.folio.ebsco.com/grafana/d/elIt9zCnz/jmeter-performance-with-average-latency?orgId=1&from=1696864147333&to=1696867911025&var-percentile=95&var-test_type=baseline&var-test=circulation_checkInCheckOut_Poppy_2&var-env=int&var-grouping=1s&var-low_limit=250&var-high_limit=750&var-db_name=jmeter&var-sampler_type=All&var-Request=All

Check-in/Check-out + Data import

http://carrier-io.int.folio.ebsco.com/grafana/d/elIt9zCnz/jmeter-performance-with-average-latency?orgId=1&from=1696927212822&to=1696931260640&var-percentile=95&var-test_type=baseline&var-test=circulation_checkInCheckOut_Poppy_2&var-env=int&var-grouping=1s&var-low_limit=250&var-high_limit=750&var-db_name=jmeter&var-sampler_type=All&var-Request=All


  • No labels