Practical experience with an application extractor for Java

  • Authors:

  • Frank Tip;Chris Laffra;Peter F. Sweeney;David Streeter

  • Affiliations:

  • IBM T.J. Watson Research Center, P.O. Box 704, Yorktown Heights, NY;IBM T.J. Watson Research Center, P.O. Box 704, Yorktown Heights, NY;IBM T.J. Watson Research Center, P.O. Box 704, Yorktown Heights, NY;IBM Toronto Laboratory, 1150 Egldnton Ave. East, Toronto, Ontario, Canada

  • Venue:
  • Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
  • Year:
  • 1999

Quantified Score

Hi-index 0.00

Visualization

Abstract

Java programs are routinely transmitted over low-bandwidth network connections as compressed class file archives (i.e., zip files and jar files). Since archive size is directly proportional to download time, it is desirable for applications to be as small as possible. This paper is concerned with the use of program transformations such as removal of dead methods and fields, inlining of method calls, and simplification of the class hierarchy for reducing application size. Such “extraction” techniques are generally believed to be especially useful for applications that use class libraries, since typically only a small fraction of a library's functionality is used. By “pruning away” unused library functionality, application size can be reduced dramatically. We implemented a number of application extraction techniques in Jax, an application extractor for Java, and evaluate their effectiveness on a set of realistic benchmarks ranging from 27 to 2,332 classes (with archives ranging from 56,796 to 3,810,120 bytes). We report archive size reductions ranging from 13.4% to 90.2% (48.7% on average).