Experiencing Slow Performance And Memory Consumption In Configurator
(Doc ID 1282401.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle Configurator - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10]Information in this document applies to any platform.
Symptoms
On Configurator Build 11.5.10.2 and Java Version "1.6.0_17" find that JVM memory is consumed fully when running multiple Configurator sessions and working on a deep model for more than 10 minutes. Seven Configurator sessions were spread across 4 JVMs. Each session configured the same model - a three-level deep multiple instantiation PTO model. It is suspected that when adding more than 20 instances of either the 2nd or 3rd level, that the memory issue occurs.
Customer monitored the memory heap size in the JVM and noticed that the available 2GB of memory is consumed / allocated very quickly. Once it happens then the CPU consumption of the JVM process goes to 100% the user experiences sluggish performance and in the past also got out of memory errors. Customer tried to compensate this with adding more JVMs so they defined 4 JVM at 2GB each and notice the same behaviour on the Application Server. During reproduction exercise, Customer tried to avoid executing database intensive tasks and limited the test to Navigation and updates on the screen without saving anything.
Customer started a performance improvement initiative that included: purchasing new servers (faster CPUs and newer technology), expanding from 2 apps servers to 3 servers, setting all Oracle recommended parameters explained in <> (including parallel garbage collection). Customer upgraded developer suite and migrated from jinit to the Java Plug-in. Last week Customer also applied ATG-7. Customer is running on a three node RAC. Customer has only one model so JVM Cache balancing will not help.
Customer settings in jserv.properties are listed below:
wrapper.bin.parameters=-verbose:gc -Xmx2048M -Xms2048M -XX:MaxPermSize=256M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC -XX:ParallelGCThreads=4
EXPECTED BEHAVIOR
-----------------------
Expect that JVM memory should not be totally consumed so quickly.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Work on Configurator for more than 10 min.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot enter/modify quotes.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |