Reducing garbage in Java

Authors:
C. E. McDowell
Affiliations:
Computer Science Dept, University of California Santa Cruz
Venue:
ACM SIGPLAN Notices
Year:
1998

Citing 0
Cited 5

Escape analysis for object-oriented languages: application to Java

Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Removing unnecessary synchronization in Java

Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Escape analysis for JavaTM: Theory and practice

ACM Transactions on Programming Languages and Systems (TOPLAS)
Heap reference analysis using access graphs

ACM Transactions on Programming Languages and Systems (TOPLAS)
Stack allocation of objects in the CACAO virtual machine

PPPJ '09 Proceedings of the 7th International Conference on Principles and Practice of Programming in Java

Quantified Score

Hi-index	0.00

Visualization

Abstract

One of the important advantages of Java, from a programmers prospective, is the use of garbage collection. One aspect of memory management in Java is that all objects are created on a garbage collected heap. Only primitive types, mostly numeric types and references to objects, are allocated on the runtime stack. We speculated that a significant number of objects behaved like traditional automatic variables, that are normally allocated on the runtime stack. We instrumented a Java virtual machine to test this hypothesis. The percentage of objects that could have been allocated on a stack instead of on the heap ranged from zero to possibly as high as 56%, but were generally in the 5--15% range.