Inlining java native calls at runtime

Stepanian, Levon; Brown, Angela Demke; Kielstra, Allan; Koblents, Gita; Stoodley, Kevin

doi:10.1145/1064979.1064997

Cited by 31 publications

(17 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As we can see, the performance gap is so wide that some optimizations are called for. A native call inlining mechanism was presented by Levon Stepanian et al [20] to eliminate the JNI call-out and call-back overheads. Here, without the necessity of modifying Android's DVM, we focus on optimizing the call-back overhead to improve the quality of generated native code.…”

Section: Optimizationsmentioning

confidence: 99%

See 1 more Smart Citation

A method-based ahead-of-time compiler for android applications

Wang

Pérez

Chung

et al. 2011

Proceedings of the 14th International Conference on Compilers, Architectures and Synthesis for Embedded Systems

View full text Add to dashboard Cite

The execution environment of Android system is based on a virtual machine called Dalvik virtual machine (DVM) in which the execution of an application program is in interpret-mode. To reduce the interpretation overhead of DVM, Google has included a trace-based just-in-time compiler (JITC) in the latest version of Android. Due to limited resources and the requirement for reasonable response time, the JITC is unable to apply deep optimizations to generate high quality code. In this paper, we propose a method-based ahead-of-time compiler (AOTC), called Icing, to speed up the execution of Android applications without the modification of any components of Android framework. The main idea of Icing is to convert the hot methods of an application program from DEX code to C code and uses the GCC compiler to translate the C code to the corresponding native code. With the Java Native Interface (JNI) library, the translated native code can be called by DVM. Both AOTC and JITC have their strength and weakness. In order to combine the strength and avoid the weakness of AOTC and JITC, in Icing, we have proposed a cost model to determine whether a method should be handled by AOTC or JITC during profiling. To evaluate the performance of Icing, four benchmarks used by Google JITC are used as test cases. The performance results show that, with Icing, the execution time of an application is two to three times faster than that without JITC, and 25% to 110% faster than that with JITC.

show abstract

Section: Optimizationsmentioning

confidence: 99%

“…Levon Stepanian et al [20] proposed a mechanism to reduce the JNI overhead, which is to inline the native calls with the help of JIT compiler's inlining optimization. Therefore, the native code will be executed in the JVM's context.…”

Section: Related Workmentioning

confidence: 99%

A method-based ahead-of-time compiler for android applications

Wang

Pérez

Chung

et al. 2011

Proceedings of the 14th International Conference on Compilers, Architectures and Synthesis for Embedded Systems

View full text Add to dashboard Cite

show abstract

“…There is an performance bonus of 5%-10% achieved using our technique. As we have seen by inlining the JNI calls [7] there can be a gain in the performance but these are not applied to the android JNI as it is new to the market. The Janet [8] provides the programmer an easy way to integrate the JNI and Java with type safe and static error checking.…”

Section: Resultsmentioning

confidence: 99%

“…The callbacks to the JNI are transformed into their equivalent lightweight operations [7]. IBM TR JIT [7] compiler is used as it supports multiple JVMs and class library implementation. The control flow for the TR JIT consists of phases for intermediate language (IL) generation, optimization and code generation.…”

Section: Inlining Java Native Calls At Runtimementioning

confidence: 99%

Efficient Java Native Interface for Android Based Mobile Devices

Lee

Chandrian

2011

2011IEEE 10th International Conference on Trust, Security and Privacy in Computing and Communications

View full text Add to dashboard Cite

i ABSTRACT Currently Java is making its way into the embedded systems and mobile devices like androids. The programs written in Java are compiled into machine independent binary class byte codes. A Java Virtual Machine (JVM) executes these classes. The Java platform additionally specifies the Java Native Interface (JNI). JNI allows Java code that runs within a JVM to interoperate with applications or libraries that are written in other languages and compiled to the host CPU ISA. JNI plays an important role in embedded system as it provides a mechanism to interact with libraries specific to the platform.This thesis addresses the overhead incurred in the JNI due to reflection and serialization when objects are accessed on android based mobile devices. It provides techniques to reduce this overhead. It also provides an API to access objects through its reference through pinning its memory location. The Android emulator was used to evaluate the performance of these techniques and we observed that there was 5 -10 % performance gain in the new Java Native Interface.

show abstract

“…In order to repel the attack, it is essential to have a join point at the beginning of the synchronized block that limits the CPU usage or the size of free memory. Java provides the Java Native Interface (JNI) library for talking to an operating system via a C layer and providing the resulting data to the Java application [16]. A before advice can use Java assertions to check the CPU usage, as shown in Figure 1.…”

Section: Re-entrant Checkingmentioning

confidence: 99%

Aspect-oriented support for synchronization in parallel computing

Harbulot

Gurd

2009

Proceedings of the 1st Workshop on Linking Aspect Technology and Evolution

View full text Add to dashboard Cite

Presents case studies for, and implementations of, synchronized block join points that together augment the capabilities of join points for synchronized methods in intercepting and modifying synchronization actions in distributed, Javabased, aspect oriented software. The models are applicable in any aspect oriented environment, but emphasis is placed on compatibility with AspectJ.The power of such a join point is first illustrated by analysing some case studies. While some such examples can be handled using aspects that intercept synchronized method calls, a fully general scheme is shown to need with Java synchronized blocks. The approach for recognising the synchronized block uses context exposure to provide full control of the thread behaviour when many threads compete to be executed. The proposed join point model is enhanced with a mechanism for removal of unnecessary synchronization, which is vital for reducing overheads associated with the lock. There is also a facility for re-introducing necessary synchronization that has previously been removed.

show abstract

Inlining java native calls at runtime

Cited by 31 publications

References 20 publications

A method-based ahead-of-time compiler for android applications

A method-based ahead-of-time compiler for android applications

Efficient Java Native Interface for Android Based Mobile Devices

Aspect-oriented support for synchronization in parallel computing

Contact Info

Product

Resources

About