Generational Garbage Collection Policies

Xufeng Zhao (), Syouji Nakamura () and Cunhua Qian ()
Additional contact information
Xufeng Zhao: Aichi Institute of Technology
Syouji Nakamura: Kinjo Gakuin University
Cunhua Qian: Nanjing University of Technology

A chapter in Stochastic Reliability and Maintenance Modeling, 2013, pp 333-360 from Springer

Abstract: Abstract In the computer science community, the technique of garbage collection [5] is an automatic process of memory recycling, which refers to those objects in the memory no longer referenced by programs are called garbage and should be thrown away. A garbage collector determines which objects are garbage and makes the heap space occupied by such garbage available again for the subsequent new objects. Garbage collection plays an important role in Java’s security strategy, however, it adds a large overhead that can deteriorate the program performances. From related studies which are summarized in [5], a garbage collector spends between 25 and 40 percent of execution time of programs for its work in general, and delays caused by such garbage collection are obtrusive.

Keywords: Collection Time; Cost Rate; Garbage Collection; Pause Time; Garbage Collector (search for similar items in EconPapers)
Date: 2013
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:ssrchp:978-1-4471-4971-2_15

Ordering information: This item can be ordered from
http://www.springer.com/9781447149712

DOI: 10.1007/978-1-4471-4971-2_15

Access Statistics for this chapter

More chapters in Springer Series in Reliability Engineering from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().