Batch Performance Issues Due To Hibernate Cache On Algorithms
(Doc ID 2563370.1)
Last updated on AUGUST 02, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On RMB v22.214.171.124.0 against FW v126.96.36.199.0:
We are facing performance issue whenever we have a hibernate batched data processed in Algorithms. This hibernate batched process took 6 hrs to create approximately. 2000 transactions.
Auto flush triggered by framework takes maximum of time due to which processing in JVM slows down, Primary analysis indicates the Hibernate cache is slowing down as it holds uncommitted entities, eventually causing batch performance issues.
ORMB Batch is multithreaded.
In GetJobWork - Master data id's are passed to threadpoolworkers as workunits.
In executeWorkUnits - We do BO status transition on this master data, which invokes BO Life Cycle on these entities.
Life cycle further invoke respective status algorithms and processes hibernate batched inserts/updates (creating ft's etc)
This is single commit process. Initially processing is faster but gradually when uncommitted data increases in VM, Auto flush starts running slow. We are facing this issue in multiple ORMB batches (including consulting and product) where hibernate batched operation is slowed down due to auto flush.
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