Search

Garbage Collection, Part 1 – Different object life cycles requires different garbage collection

“Under the Hood” blog series – getting a deeper technical insight like the mobile solutions, JVM, computer languages, scripts, databases and other interesting tools and technologies. Each blog in this series is a result from our experiences, customer projects and gained knowledge through the web community.

Java’s memory model in the runtime data area is separated into three different parts: the heap, method area and native area. It is managed by several garbage collectors. In this blog I will explain about objects with different life cycles, its effects during creation until termination (garbage collection), and the necessity of having different ergonomics and garbage collections.

Read more

JVM Memory Arguments

“Cookbook” blog series – a collection of best practices for solving problems. Each blog in this series is a result from our experiences, customer projects and gained knowledge through the web community.

Problem

You want to optimize your Java memory. For example an OutOfMemoryError can occur in several parts of Java’s Runtime Data Area: in the young or old generation of the heap space, permanent generation or code cache of the non-heap area.

Read more

Runtime Data Areas – Java’s Memory Model

“Under the Hood” blog series – getting a deeper technical insight like the mobile solutions, JVM, computer languages, scripts, databases and other interesting tools and technologies. Each blog in this series is a result from our experiences, customer projects and gained knowledge through the web community.

Every developer gets once confronted by Java memory questions like: What size should I define for the Heap space? An OutOfMemoryError covers which part of the runtime data area? In the Heap, PermGen, or Thread? And how do I solve it?

Read more