Improved Ahead-of-time Compilation of Stack-based JVM Bytecode on Resource-constrained Devices

Abstract

Many virtual machines exist for sensor nodes with only a few KB RAM and tens to a few hundred KB flash memory. They pack an impressive set of features, but suffer from a slowdown of one to two orders of magnitude compared to optimised native code, reducing throughput and increasing power consumption.Compiling bytecode to native code to improve performance has been studied extensively for larger devices, but the restricted resources on sensor nodes mean most modern techniques cannot be applied. Simply replacing bytecode instructions with predefined sequences of native instructions is known to improve performance, but produces code several times larger than the optimised C equivalent, limiting the size of programmes that can fit onto a device. This paper identifies the major sources of overhead resulting from this basic approach, and presents optimisations to remove most of the remaining performance overhead, and over half the size overhead, reducing them to 69% and 91% respectively. While this increases the size of the VM, the break-even point at which this fixed cost is compensated for is well within the range of memory available on a sensor device, allowing us to both improve performance and load more code on a device.

Distributed Symbolic Network Quality Assessment for Resource-constrained Devices

“…Alternatively, interpreted languages enable the dynamic execution of programs speeding up the development process, and allowing debugging and modifications to the programs even at runtime. These interpreters usually run atop a generalpurpose operating system or need to be embedded inside an application [17], dramatically increasing resource consumption and memory occupation [18], and limiting the access to the underlying hardware.…”

IoT Sensing Networks for Gait Velocity Measurement

“…Different from traditional JVM, the Darjeeling VM uses the AOT (Ahead-of-Time) compiler rather than the JIT, to reduce the memory and storage usage requirements. The memory footprint of DarjeelingVM is less than 80 kB and the optimized Java executable code is only 86% slower than the optimized native C executable code (Reijers and Shih, 2017). (Other Java JIT compilers are from 30 to 200 times slower compared with the optimized C implementation.…”