What's the Consequence of Having an Oversized Java Heap?
(Doc ID 2788231.1)
Last updated on MAY 01, 2024
Applies to:
Oracle WebLogic Server - Version 10.3.6 and laterInformation in this document applies to any platform.
Symptoms
A system should use the resources that it requires, no more, no less. This is valid for stable systems not affected to memory leak.
That will lead us to the next question. What's the right size for my heap? That's a fine-tuning issue and it can be addressed with the information provided by the GC log file collected during a representative period of time, for example, during 1 week. If the system is sensitive to some seasons (black Friday, Christmas eve, etc) you'd better collect the GC log during that moment. Typically, collecting a GC log file doesn't affect the performance of the system. The idea is to collect a representative sample for the operation of the system under normal conditions.
Assuming the GC log file won't present indications of memory leak, choosing the incorrect size for the heap could have direct consequences:
-
OutOfMemory if the size is too small
-
Long GC pause if the size is too large
Having said that, the next step is starting up the Java process with the GC log flags:
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 |