Nitan Singh | University of Jammu (original) (raw)
Supervisors: Dr. Shubhnandan S. Jamwal and Prof. Devanand
Phone: 9906074532
Address: Department of Computer Science & IT
Jammu University
less
Uploads
Papers by Nitan Singh
Garbage Collection (GC) is a process of automatic memory reclamation from the objects that are no... more Garbage Collection (GC) is a process of automatic memory reclamation from the objects that are no longer required by the mutator. The execution time of the application and memory reclaimed by garbage collector are important factors that influence the selection of a specific garbage collector while selecting a specific one. The current research paper selects a suitable garbage collector on the basis of the above mentioned two factors. In this paper the execution time of SPECjvm2008 benchmarks and memory reclaimed by a garbage collector while executing these application is determined in real JVM. We further propose the optimal values of the above two issues that can be compromised, if the an application is to be executed with the garbage collector.
With the advent of pure object oriented languages like Java and C# the problem of automatic stora... more With the advent of pure object oriented languages like Java and C# the problem of automatic storage reclamation or automatic memory management is solved by GC and there are several metrics which influence the performance of every GC. The most important metrics are Application Execution Time, Number of Pauses (minor/major), and Average time taken for each pause (minor/major), Throughput. In the current research different parameters for different types of applications have been found. These parameters can be used for setting the environment for GC before its invocation for a particular type of benchmark. The findings are based on the tests which have been performed on SPECjvm2008. Based on the results obtained, it has been proposed that selection of a particular GC and setting of the parameters for a specific application should be done before the invocation of a specific GC.
Many object-oriented programming languages like Java and C# are gaining importance in the develop... more Many object-oriented programming languages like Java and C# are gaining importance in the development of reliable and robust applications because of the presence of Garbage Collectors. There are multiple Garbage Collectors (GC) available in JDK 1.7.0_04. In the current research we compared the performance of serial and parallel collectors with respect to SPECjvm2008. It has been found that the behavior of the Garbage Collector is application specific. Not all the benchmarks require same size of heap for its invocation. There is considerable amount of difference in heap size for initialization of Garbage Collector. The value of optimal size of the heap varies from 100 megabyte (mb) to 400 mb for different benchmarks. In the current research, benchmarks available in SPECjvm2008 are considered over a wide range of Heap size.
Garbage Collection (GC) is a process of automatic memory reclamation from the objects that are no... more Garbage Collection (GC) is a process of automatic memory reclamation from the objects that are no longer required by the mutator. The execution time of the application and memory reclaimed by garbage collector are important factors that influence the selection of a specific garbage collector while selecting a specific one. The current research paper selects a suitable garbage collector on the basis of the above mentioned two factors. In this paper the execution time of SPECjvm2008 benchmarks and memory reclaimed by a garbage collector while executing these application is determined in real JVM. We further propose the optimal values of the above two issues that can be compromised, if the an application is to be executed with the garbage collector.
With the advent of pure object oriented languages like Java and C# the problem of automatic stora... more With the advent of pure object oriented languages like Java and C# the problem of automatic storage reclamation or automatic memory management is solved by GC and there are several metrics which influence the performance of every GC. The most important metrics are Application Execution Time, Number of Pauses (minor/major), and Average time taken for each pause (minor/major), Throughput. In the current research different parameters for different types of applications have been found. These parameters can be used for setting the environment for GC before its invocation for a particular type of benchmark. The findings are based on the tests which have been performed on SPECjvm2008. Based on the results obtained, it has been proposed that selection of a particular GC and setting of the parameters for a specific application should be done before the invocation of a specific GC.
Many object-oriented programming languages like Java and C# are gaining importance in the develop... more Many object-oriented programming languages like Java and C# are gaining importance in the development of reliable and robust applications because of the presence of Garbage Collectors. There are multiple Garbage Collectors (GC) available in JDK 1.7.0_04. In the current research we compared the performance of serial and parallel collectors with respect to SPECjvm2008. It has been found that the behavior of the Garbage Collector is application specific. Not all the benchmarks require same size of heap for its invocation. There is considerable amount of difference in heap size for initialization of Garbage Collector. The value of optimal size of the heap varies from 100 megabyte (mb) to 400 mb for different benchmarks. In the current research, benchmarks available in SPECjvm2008 are considered over a wide range of Heap size.