OutOfMemory, Churn Rate and more - Java Enterprise Performance Book (dynaTrace)
Out-Of-Memory Errors Out-of-memory errors occur when there is not enough space available in the heap to create a new object. A JVM will always trigger a garbage collection and try to reclaim memory before raising an out-of-memory error. In most cases the underlying cause is an insufficient memory configuration or a memory leak, but there are some others. Here is a non-exhaustive list of the most important ones: Insufficient memory configuration Allocating oversized temporary objects Besides the first two, mMemory fragmentation can also cause out-of-memory errors even when there appears to be enough free memory, because there isn't a single continuous area in the heap that's large enough for the allocation request. In most cases, compaction assures that this does not occur, however there are GC strategies that do not use compaction. Some JVM implementations, such as the Oracle HotSpot, will throw an out-of-memory error when GC overhead becomes too great.Read full article from OutOfMemory, Churn Rate and more - Java Enterprise Performance Book (dynaTrace)
No comments:
Post a Comment