High Heap Usage Seen When Using Exalogic Tuning Agent
(Doc ID 2478167.1)
Last updated on OCTOBER 08, 2019
Applies to:Oracle TopLink - Version 220.127.116.11 to 18.104.22.168.0 [Release 12c]
Information in this document applies to any platform.
You have a web application running on a Exalogic Machine with Exalogic Optimizations enabled. You notice this domain is experiencing a lot of time spent in GC and that the web application response is becoming very slow. High Java Heap usage is being seen on the web application, which is using the "oracle.toplink.exalogic.tuning.TuningAgent". Below is a description of the Exalogic Tuning Agent:
"TopLink includes an automated tuner that provides an optimized configuration or the Exalogic platform. It enables multiple performance features and
enables an Exalogic-specific profiler. The profiler monitors the startup phase of the application and detects queries that trigger the n+1 query
execution problem. It then optimizes these queries to use batch fetching. For dynamic queries that cannot use batch fetching, it further analyses these
queries and defines a runtime state machine to detect and optimize these queries"
For more see here.
A full restart may be necessary to restore performance.
Why does 'oracle.toplink.exalogic.tuning.TuningAgent' seem to be the cause of this issue?
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