ACM Home Page
Please provide us with feedback. Feedback
The design, implementation, and evaluation of adaptive code unloading for resource-constrained devices
Full text PdfPdf (814 KB)
Source ACM Transactions on Architecture and Code Optimization (TACO) archive
Volume 2 ,  Issue 2  (June 2005) table of contents
Pages: 131 - 164  
Year of Publication: 2005
ISSN:1544-3566
Authors
Lingli Zhang  University of California, Santa Barbara, CA
Chandra Krintz  University of California, Santa Barbara, CA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 68,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1071604.1071606
What is a DOI?

ABSTRACT

Java Virtual Machines (JVMs) for resource-constrained devices, e.g., hand-helds and cell phones, commonly employ interpretation for program translation. However, compilers are able to produce significantly better code quality, and, hence, use device resources more efficiently than interpreters, since compilers can consider large sections of code concurrently and exploit optimization opportunities. Moreover, compilation-based systems store code for reuse by future invocations obviating the redundant computation required for reinterpretation of repeatedly executed code.However, code storage required for compilation can increase the memory footprint of the virtual machine (VM) significantly. As a result, for devices with limited memory resources, this additional code storage may preclude some programs from executing, significantly increase memory management overhead, and substantially reduce the amount of memory available for use by the application.To address the limitations of native code storage, we present the design, implementation, and empirical evaluation of a compiled-code management system that can be integrated into any compilation-based JVM. The system unloads compiled code to reduce the memory footprint of the VM. It does so by dynamically identifying and unloading dead or infrequently used code; if the code is later reused, it is recompiled by the system. As such, our system adaptively trades off memory footprint and its associated memory management costs, with recompilation overhead. Our empirical evaluation shows that our code management system significantly reduces the memory requirements of a compile-only JVM, while maintaining the performance benefits enabled by compilation.We investigate a number of implementation alternatives that use dynamic program behavior and system resource availability to determine when to unload as well as what code to unload. From our empirical evaluation of these alternatives, we identify a set of strategies that enable significant reductions in the memory overhead required for application code. Our system reduces code size by 36--62%, on average, which translates into significant execution-time benefits for the benchmarks and JVM configurations that we studied.


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
Arnold, M., Fink, S., Grove, D., Hind, M., and Sweeney, P. F. 2000b. Adaptive optimization in the Jalapeño JVM: The controller's analytical mode. In Proceedings of the 3rd ACM Workshop on Feedback-Directed and Dynamic Optimization (FDDO-3).
5
 
6
 
7
 
8
Bruening, D. and Duesterwald, E. 2000. Exploring optimal compilation unit shapes for an embedded Just-In-Time compiler. In Proceedings of the 3rd ACM Workshop on Feedback-Directed and Dynamic Optimization (FDDO-3).
 
9
 
10
ChaiVM. http://www.chai.hp.com.
11
 
12
CLDC 2003. The cldc hotspot(tm) implementation virtual machine. White Paper. http://web2.java.sun.com/products/cldc/wp/CLDC_HotSpot_WhitePaper.pdf.
13
 
14
 
15
 
16
 
17
18
19
 
20
 
21
 
22
 
23
 
24
HotSpot 2001. The Java HotSpot Virtual Machine. White Paper. http://java.sun.com/products/hotspot/docs/whitepaper/Java_HotSpot_WP_Final_4_30_01.ps.
 
25
Kaffe 1998. Kaffe---An opensource Java virtual machine. http://www.kaffe.org.
 
26
 
27
28
 
29
Krintz, C., Grove, D., Sarkar, V., and Calder, B. 2001. Reducing the overhead of dynamic compilation. Software-Practice and Experience 31, 8, 717--738.
 
30
KVM 2000. Java(TM) 2 Platform Micro Edition(J2ME(TM)) Technology for creating mobile devices. White Paper. http://java.sun.com/products/cldc/wp/KVMwp.pdf.
 
31
32
 
33
SpecJVM98. SpecJVM'98 Benchmarks. http://www.spec.org/osg/jvm98.
 
34
SSCLI 2002. Rotor - the shared source cli. http://research.microsoft.com/programs/europe/rotor/default.aspx.
 
35
 
36
 
37
Takahashi, D. 2001. Java chips make a comeback. Red Herring.
 
38
Vijaykrishnan, N., Kandemir, M., Tomar, S., Kim, S., Sivasubramaniam, A., and Irwin, M. J. 2001. Energy characterization of Java applications from a memory perspective. In Proceedings of the USENIX Java Virtual Machine Research and Technology Symposium.
39
 
40
41
 
42



REVIEW

"Peter Patton : Reviewer"

An interesting issue with small resource-limited handheld devices and cellular phones, for which Java and its Java Virtual Machine (JVM) interpreter were originally designed, is addressed in this paper. Recent developments in Java compilation allo  more...

Collaborative Colleagues:
Lingli Zhang: colleagues
Chandra Krintz: colleagues