Done
Details
Assignee
Roman BarannykRoman BarannykReporter
Martin TranMartin TranPriority
P2Story Points
3Sprint
NoneDevelopment Team
VegaRelease
Poppy (R2 2023) Bug FixRCA Group
Implementation coding issueTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Roman Barannyk
Roman BarannykReporter
Martin Tran
Martin TranPriority
Story Points
3
Sprint
None
Development Team
Vega
Release
Poppy (R2 2023) Bug Fix
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 16, 2023 at 10:29 PM
Updated March 20, 2024 at 2:32 PM
Resolved December 4, 2023 at 12:03 PM
Performance tests of the Check In/Out workflows show that in Poppy mod-pubsub has a memory leak. Details from https://folio-org.atlassian.net/browse/PERF-721#icft=PERF-721:
Longevity test was conducted for CICO on pcp1 (75 users, 8 hours). During this test mod-pubsub memory consumption increased from 37% to 63%.
Class taking most of the memory - "java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue". At the end of the test it occupies 95% of bytes. There is a big number of events like java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask inside the class. Number of these events at the beginning of the test - 83K, number at the end of the test - 840K.
Please see https://folio-org.atlassian.net/browse/PERF-721#icft=PERF-721 for more details.