ACM Home Page
Please provide us with feedback. Feedback
Beltway: getting around garbage collection gridlock
Full text PdfPdf (185 KB)
Source Conference on Programming Language Design and Implementation archive
Proceedings of the ACM SIGPLAN 2002 Conference on Programming language design and implementation table of contents
Berlin, Germany
SESSION: Garbage Collection table of contents
Pages: 153 - 164  
Year of Publication: 2002
ISBN:1-58113-463-0
Also published in ...
Authors
Stephen M Blackburn  Australian National University, Canberra, ACT, 0200, Australia
Richard Jones  University of Kent, Canterbury, Kent, CT2 7NF, UK
Kathryn S. McKinley  University of Texas at Austin, Austin, TX
J Eliot B Moss  University of Massachusetts, Amherst, MA
Sponsor
SIGPLAN: ACM Special Interest Group on Programming Languages
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 89,   Citation Count: 31
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/512529.512548
What is a DOI?

ABSTRACT

We present the design and implementation of a new garbage collection framework that significantly generalizes existing copying collectors. The Beltway framework exploits and separates object age and incrementality. It groups objects in one or more increments on queues called belts, collects belts independently, and collects increments on a belt in first-in-first-out order. We show that Beltway configurations, selected by command line options, act and perform the same as semi-space, generational, and older-first collectors, and encompass all previous copying collectors of which we are aware. The increasing reliance on garbage collected languages such as Java requires that the collector perform well. We show that the generality of Beltway enables us to design and implement new collectors that are robust to variations in heap size and improve total execution time over the best generational copying collectors of which we are aware by up to 40%, and on average by 5 to 10%, for small to moderate heap sizes. New garbage collection algorithms are rare, and yet we define not just one, but a new family of collectors that subsumes previous work. This generality enables us to explore a larger design space and build better collectors.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
 
3
4
 
5
David A. Barrett and Benjamin Zorn. Garbage collection using a dynamic threatening boundary. Computer Science Technical Report CU-CS-659-93, University of Colorado, July 1993
 
6
Peter B. Bishop. Computer Systems with a Very Large Address Space and Garbage Collection. PhD thesis, MIT Laboratory for Computer Science, May 1977. Technical report MIT/LCS/TR--178
7
8
9
10
11
12
13
14
15
16
 
17
18
 
19
Lars Thomas Hansen. Older-first garbage collection in practice. PhD thesis, North-eastern University, November 2000
20
21
22
23
 
24
 
25
26
 
27
John H. Reppy. A high-performance garbage collector for Standard ML. Technical memorandum, AT&T Bell Laboratories, Murray Hill, NJ, December 1993
 
28
Standard Performance Evaluation Corporation. SPECjvm98 Documentation, release 1.03 edition, March 1999
 
29
Standard Performance Evaluation Corporation. SPECjbb2000 (Java Business Benchmark) Documentation, release 1.01 edition, 2001
30
 
31
32
 
33
34
35
 
36
37
 
38
39
 
40

CITED BY  31

Collaborative Colleagues:
Stephen M Blackburn: colleagues
Richard Jones: colleagues
Kathryn S. McKinley: colleagues
J Eliot B Moss: colleagues