Jolt

Shankar, Ajeet; Arnold, Matthew; Bodík, Rastislav

doi:10.1145/1449764.1449775

Cited by 65 publications

(3 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There also exists a body of JVM-based profiling techniques [21,36,43,49,[57][58][59] that are used primarily to detect performance problems. Sampling-based Profiling.…”

Section: Performance Of Decoding and Recoverymentioning

confidence: 99%

JPortal: precise and efficient control-flow tracing for JVM programs with Intel processor trace

Zuo

Jiao

Wang

et al. 2021

Proceedings of the 42nd ACM SIGPLAN International Conference on Programming Language Design and Implementation

View full text Add to dashboard Cite

Hardware tracing modules such as Intel Processor Trace perform continuous control-flow tracing of an end-to-end program execution with an ultra-low overhead. PT has been used in a variety of contexts to support applications such as testing, debugging, and performance diagnosis. However, these hardware modules have so far been used only to trace native programs, which are directly compiled down to machine code. As high-level languages (HLL) such as Java and Go become increasingly popular, there is a pressing need to extend these benefits to the HLL community. This paper presents JPortal, a JVM-based profiling tool that bridges the gap between HLL applications and low-level hardware traces by using a set of algorithms to precisely recover an HLL program's control flow from PT traces. An evaluation of JPortal with the DaCapo benchmark shows that JPortal achieves an overall 80% accuracy for end-to-end control flow profiling with only a 4-16% runtime overhead.

show abstract

“…There also exists a body of JVM-based profiling techniques [21,36,43,49,[57][58][59] that are used primarily to detect performance problems. Sampling-based Profiling.…”

Section: Performance Of Decoding and Recoverymentioning

confidence: 99%

JPortal: precise and efficient control-flow tracing for JVM programs with Intel processor trace

Zuo

Jiao

Wang

et al. 2021

Proceedings of the 42nd ACM SIGPLAN International Conference on Programming Language Design and Implementation

View full text Add to dashboard Cite

show abstract

“…Researchers have proposed profiling and program analysis techniques to identify runtime bloat. In general, software bloat is identified using heuristic‐based approaches such as profile the number of instances of certain object type or observing the time between the creation and garbage collection of object instances . Dufour et al have proposed an approach combining both dynamic and static analysis.…”

Section: Mitigating Issues Of Opportunistic Reuse Practicementioning

confidence: 99%

“…Because of the large memory footprint of a software, they use dynamic analysis to observe the objects life, and then use static analysis techniques to locate suspicious source code fragments. Similarly, Shankar et al propose an approach based on escape analysis to avoid object churn. They define object churn as harmful, which is caused due to rapid creation of many short lived objects.…”

Section: Mitigating Issues Of Opportunistic Reuse Practicementioning

confidence: 99%

Perils of opportunistically reusing software module

Kulkarni

Varma

2016

Softw Pract Exp

View full text Add to dashboard Cite

Summary Opportunistic reuse is a need based sourcing of software modules without a prior reuse plan. It is a common tactical approach in software development. Developers often reuse an external software module opportunistically to improve their productivity. But, studies have shown that this results in extensive refactoring and adds maintenance owes. We assert this problem to the mismatches between the software under development and the reused external module; caused because of their different assumptions and constraints. We highlight the problems of such opportunistic reuse practices with the help of a case study. In our study, we found issues such as unanticipated behavior, violated constraints, conflict in assumption, fragile structure, and software bloat. In this paper, we like to draw attention of the research community to the wide spread opportunistic reuse practices and the lack of methods to pro‐actively identify and resolve the mismatches. We propose the need for supporting developers in reasoning before reuse from the perspective of identifying and fixing both local and global mismatches. Furthermore, we identify other opportunistic software development practices where similar issues can be observed and also suggest the research areas where further investigation can benefit developers in improving their productivity. Copyright © 2016 John Wiley & Sons, Ltd.

show abstract

Workload characterization of JVM languages

Sarimbekov

Mössenböck

Bulej

et al. 2015

Softw. Pract. Exper.

View full text Add to dashboard Cite

SUMMARYOriginally developed with a single language in mind, the JVM is now targeted by numerous programming languages-its automatic memory management, just-in-time compilation, and adaptive optimizationsmaking it an attractive execution platform. However, the garbage collector, the just-in-time compiler, and other optimizations and heuristics were designed primarily with the performance of Java programs in mind. Consequently, many of the languages targeting the JVM, and especially the dynamically typed languages, are suffering from performance problems that cannot be simply solved at the JVM side. In this article, we aim to contribute to the understanding of the character of the workloads imposed on the JVM by both dynamically typed and statically typed JVM languages. To this end, we introduce a new set of dynamic metrics for workload characterization, along with an easy-to-use toolchain to collect the metrics. We apply the toolchain to applications written in six JVM languages (Java, Scala, Clojure, Jython, JRuby, and JavaScript) and discuss the findings. Given the recently identified importance of inlining for the performance of Scala programs, we also analyze the inlining behavior of the HotSpot JVM when executing bytecode originating from different JVM languages. As a result, we identify several traits in the non-Java workloads that represent potential opportunities for optimization.

show abstract

Jolt

Cited by 65 publications

References 21 publications

JPortal: precise and efficient control-flow tracing for JVM programs with Intel processor trace

JPortal: precise and efficient control-flow tracing for JVM programs with Intel processor trace

Perils of opportunistically reusing software module

Workload characterization of JVM languages

Contact Info

Product

Resources

About