implement-auto-instrumentation-under-graalvm-static-compilation-on-otel-java-agent-graalvm-bi-bi-gan-otel-java-agent-zha-kek-jiong-zihao-rao-alibaba-cloud.pdf

1、Implement Auto Instrumentation Under GraalVM Static Compilation on OTel Java AgentZihao Rao,Alibaba CloudBackground01Part OneSolution02Part TwoDemonstration03Part ThreeFuture works04Part FourBackgroundChallenges for modern Java applicationsSlowstartupHighmemory overheadLifecycle of Java applications

2、:VM init,App init,warmup,App active and shutdown:Picture by:https:/ of Java apps Introduction of GraalVM native imagePicture by:https:/ to JVM-based environments,GraalVM offers the following advantagesEnhanced startup speed:By eliminating VM init,JIT,and interpretation overhead,the startup time is s

3、ignificantly reducedReduced memory overhead:By removing the memory footprint associated with the VM and applying numerous optimizations,memory usage is significantly reducedLifecycle of Java apps under GraalVMImprovements of different frameworks.javaJava codeJava bytecodejavacNative CompileRunNative

4、 ImageJVMOperating SystemComparation of JVM and native compilation.classGraalVM native image compilation processPicture by:https:/ of native compilationThe process of native compile:Impacts of GraalVM on the Java EcosystemDynamic Features:Dynamic class loading,reflection,dynamic proxies,JNI,and seri

5、alization are no longer fully supportedPlatform Independence:Without the JVM and bytecode,the platform independence that is a hallmark of the Java platform is no longer availableEcosystem Tools:The original Java ecosystem tools for monitoring,debugging,and Java Agents are ineffective without the JVM

6、 and bytecodeOTel CollectorMicroservicesOTel AgentFrontends&APIsDatabasesImpact of GraalVM in observabilitySolutionWith GraalVM,bytecode is no longer used.Therefore,we aim to perform these enhancements during compilation:Idea to instrument under GraalVMJava Agent work process:java-javaagent:agent.ja