CloudJIT: A Just-in-Time FaaS Optimizer (Work in Progress)
summary
Platform prototype automatically detects hot functions and AOT-compiles them with GraalVM native-image, keeping the rest on the JVM; AOT runs in parallel via a native-image builder after collecting runtime config with an agent. A single-cluster evaluation compiles 27% of functions, 30% of cold starts optimized and cuts memory ~30%, while acknowledging AOT takes minutes, needs high CPU/memory, and requires extra config to avoid closed‑world/reflection misses.
AI-written summary · about
chapters (7)
- 0:00FaaS and CloudJIT intro
- 1:50Slow call starts in FaaS
- 3:39Ahead-of-time compilation
- 6:10CloudJIT: FaaS optimizer
- 8:58Evaluation results
- 9:40Future work and conclusion
- 10:27Q&A
related talks
41mGraal: How to use the new JVM JIT compiler in real life
51mGoing AOT: Everything you need to know about GraalVM for Java applications
56mMaximizing Performance with GraalVM
45mMicronaut AOT: Optimizing Your Applications for the JIT and GraalVM
29mThe Next Frontier in Open Source Java Compilers: Just-in-Time Compilation as a Service
44mJava In The Cloud with GraalVM
42mJava in the Cloud with GraalVM
38mThe Next Frontier in Open Source Java Compilers: Just-In-Time Compilation as a Service
