A unifying approach to performance analysis in the Java environment

Alexander, W. P.; Berry, Robert F.; Levine, F. E.; Urquhart, Robert

doi:10.1147/sj.391.0118

Cited by 15 publications

(9 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This is achieved by propagating visible instances backwards in the CCT. 1 The reduced connection graph also elides edges other than those that represent points-to relationships between objects through their reference fields.…”

Section: Blended Escape Analysismentioning

confidence: 99%

See 1 more Smart Citation

A scalable technique for characterizing the usage of temporaries in framework-intensive Java applications

Dufour

Ryder

Sevitsky

2008

Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering

View full text Add to dashboard Cite

Framework-intensive applications (e.g., Web applications) heavily use temporary data structures, often resulting in performance bottlenecks. This paper presents an optimized blended escape analysis to approximate object lifetimes and thus, to identify these temporaries and their uses. Empirical results show that this optimized analysis on average prunes 37% of the basic blocks in our benchmarks, and achieves a speedup of up to 29 times compared to the original analysis. Newly defined metrics quantify key properties of temporary data structures and their uses. A detailed empirical evaluation offers the first characterization of temporaries in frameworkintensive applications. The results show that temporary data structures can include up to 12 distinct object types and can traverse through as many as 14 method invocations before being captured.

show abstract

Section: Blended Escape Analysismentioning

confidence: 99%

“…In such cases, understanding the purpose of a single object requires studying its role within a data structure. Existing profiling tools like Jinsight [10] and ArcFlow [1] focus on the allocating methods of individual objects, and therefore do not provide information regarding how objects are used.…”

Section: Introductionmentioning

confidence: 99%

A scalable technique for characterizing the usage of temporaries in framework-intensive Java applications

Dufour

Ryder

Sevitsky

2008

Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering

View full text Add to dashboard Cite

show abstract

“…That is, if a method is executed in MMI first, and then promoted to level-1, it is counted only in level-1 execution mode. For the execution time in each execution mode, we collected the data by using a profiling tool called real-time arcflow [Alexander et al 2000]. The tool instruments at entry and exit for each method using a JVMPI interface to collect the time stamp, and then post-processes the collected data to provide the proportion of the execution time spent in each method.…”

Section: Execution Mode Ratiosmentioning

confidence: 99%

Design and evaluation of dynamic optimizations for a Java just-in-time compiler

Suganuma

Yasue

Kawahito

et al. 2005

ACM Trans. Program. Lang. Syst.

View full text Add to dashboard Cite

The high performance implementation of Java Virtual Machines (JVM) and Just-In-Time (JIT) compilers is directed toward employing a dynamic compilation system on the basis of online runtime profile information. The trade-off between the compilation overhead and performance benefit is a crucial issue for such a system. This article describes the design and implementation of a dynamic optimization framework in a production-level Java JIT compiler, together with two techniques for profile-directed optimizations: method inlining and code specialization. Our approach is to employ a mixed mode interpreter and a three-level optimizing compiler, supporting level-1 to level-3 optimizations, each of which has a different set of trade-offs between compilation overhead and execution speed. A lightweight sampling profiler operates continuously during the entire period while applications are running to monitor the programs' hot spots. Detailed information on runtime behavior can be collected by dynamically generating instrumentation code that is installed to and uninstalled from the specified recompilation target code. Value profiling with this instrumentation mechanism allows fully automatic profile-directed method inlining and code specialization to be performed on the basis of call site information or specific parameter values at the higher optimization levels. The experimental results show that our approach offers high performance and low compilation overhead in both program startup and steady state measurements in comparison to the previous systems. The two profile-directed optimization techniques contribute significant portions of the improvements.

show abstract

“…Many tools [2,3,5,6,11,13,14,16,18,19] rely on restarting or instrumenting an application, which is often forbidden in commercial deployment environments. Similarly, many organizations will not deploy any unapproved monitoring agents, nor tolerate any significant perturbation of the running system.…”

Section: Introductionmentioning

confidence: 99%

Performance analysis of idle programs

Altman

Arnold

Fink

et al. 2010

Proceedings of the ACM International Conference on Object Oriented Programming Systems Languages and Applications

View full text Add to dashboard Cite

This paper presents an approach for performance analysis of modern enterprise-class server applications. In our experience, performance bottlenecks in these applications differ qualitatively from bottlenecks in smaller, stand-alone systems. Small applications and benchmarks often suffer from CPU-intensive hot spots. In contrast, enterprise-class multi-tier applications often suffer from problems that manifest not as hot spots, but as idle time indicating a lack of forward motion. Many factors can contribute to undesirable idle time, including locking problems, excessive system-level activities like garbage collection, various resource constraints, and problems driving load.We present the design and methodology for WAIT, a tool to diagnosis the root cause of idle time in server applications. Given lightweight samples of Java activity on a single tier, the tool can often pinpoint the primary bottleneck on a multi-tier system. The methodology centers on an informative abstraction of the states of idleness observed in a running program. This abstraction allows the tool to distinguish, for example, between hold-ups on a database machine, insufficient load, lock contention in application code, and a conventional bottleneck due to a hot method. To compute the abstraction, we present a simple expert system based on an extensible set of declarative rules.WAIT can be deployed on the fly, without modifying or even restarting the application. Many groups in IBM have applied the tool to diagnosis performance problems in commercial systems, and we present a number of examples as case studies.

show abstract

A unifying approach to performance analysis in the Java environment

Cited by 15 publications

References 5 publications

A scalable technique for characterizing the usage of temporaries in framework-intensive Java applications

A scalable technique for characterizing the usage of temporaries in framework-intensive Java applications

Design and evaluation of dynamic optimizations for a Java just-in-time compiler

Performance analysis of idle programs

Contact Info

Product

Resources

About