Entry Ogasawara:2006:EED from toplas.bib

Last update: Tue May 1 02:05:46 MDT 2012                Valid HTML 3.2!

Index sections

Top | Symbols | Math | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

BibTeX entry

@Article{Ogasawara:2006:EED,
  author =       "Takeshi Ogasawara and Hideaki Komatsu and Toshio
                 Nakatani",
  title =        "{EDO}: {Exception-Directed Optimization} in {Java}",
  journal =      j-TOPLAS,
  volume =       "28",
  number =       "1",
  pages =        "70--105",
  month =        jan,
  year =         "2006",
  CODEN =        "ATPSDT",
  DOI =          "http://doi.acm.org/10.1145/1111596.1111598",
  ISSN =         "0164-0925 (print), 1558-4593 (electronic)",
  ISSN-L =       "0164-0925",
  bibdate =      "Tue Jan 24 05:55:31 MST 2006",
  bibsource =    "http://www.acm.org/pubs/contents/journals/toplas/;
                 http://www.math.utah.edu/pub/tex/bib/toplas.bib",
  abstract =     "Optimizing exception handling is critical for programs
                 that frequently throw exceptions. We observed that
                 there are many such exception-intensive programs
                 written in Java. There are two commonly used exception
                 handling techniques, stack unwinding and stack cutting.
                 Stack unwinding optimizes the normal path by leaving
                 the exception handling path unoptimized, while stack
                 cutting optimizes the exception handling path by adding
                 extra work to the normal path. However, there has been
                 no single exception handling technique to optimize the
                 exception handling path without incurring any overhead
                 to the normal path.We propose a new technique called
                 {\em Exception-Directed Optimization\/} (EDO) that
                 optimizes exception-intensive programs without slowing
                 down exception-minimal programs. It is a
                 feedback-directed dynamic optimization consisting of
                 three steps: exception path profiling, exception path
                 inlining, and throw elimination. Exception path
                 profiling attempts to detect hot exception paths.
                 Exception path inlining embeds every hot exception path
                 into the corresponding catching method. Throw
                 elimination replaces a throw with a branch to the
                 corresponding handler. We implemented EDO in IBM's
                 production Just-in-Time compiler and made several
                 experiments. In summary, it improved the performance of
                 exception-intensive programs by up to 18.3\% without
                 decreasing the performance of exception-minimal
                 programs for SPECjvm98. We also found an opportunity
                 for performance improvement using EDO in the startup of
                 a Java application server.",
  acknowledgement = ack-nhfb,
  fjournal =     "ACM Transactions on Programming Languages and
                 Systems",
}

Related entries