Incremental and Serial Garbage Collector in Small Footprints

The Java virtual machine's heap stores all objects created by a running Java application. Objects are created during the scope of the program with different methods and instructions, but never freed explicitly by the code. Garbage collection is the process of automatically freeing objects that are no longer referenced by the program. Garbage collection techniques lead to long and unpredictable delays and are therefore unsatisfactory in a number of settings, such as interactivesystems, where non-disruptivebehavior is of paramount importance. In this paper we analyzed how memory allocation and garbage collection is affected in multithreaded environments with respect to the incremental and serial garbage collector of JDK5. Our work in this paper is focused on the behavior of incremental garbage collector (INC) and Serial garbage collector (SR) in small footprints. It is observed that the memory reclamation by the incremental garbage collector is 58.83% more than the serial collector. The average time spend for the collection in case of serial garbage collector is 61.05% more than its counterpart. The memory collection in II^ndcycle of incremental garbage collector 346.59% more than the serial garbage collector. JVM is not initialized below 5mb of stack for INC but initialized at 1mb for SR GC.