Going green with native: efficient, sustainable software
summary
Live measurements compare frameworks and runtimes not promises: 155 MB jar vs 86 MB native image, startup times in milliseconds and memory down to ~70 MB heap, and benchmark runs showing tens of thousands of requests per second (Micronaut ~30k locally, native builds sustaining much higher throughput). Native builds cost build time (about 1m36s here) and require GraalVM hints for reflection, but yield lower CPU, memory, storage and faster scaling in containers.
AI-written summary · about
chapters (16)
- 0:00Green software introduction
- 1:03Defining green IT
- 2:49Hardware growth and bloat
- 4:14ICT emissions forecasts
- 5:19Low-hanging fruit for sustainable software
- 7:51Scalability reduces emissions
- 8:33Native mode benefits
- 9:17Framework performance demo
- 12:26Native apps optimize resources
- 15:18GraalVM native apps
- 17:24GraalVM build trade-offs
- 19:41Final performance tests
- 21:07Measure carbon intensity
- 21:51Cloud emissions tools
- 23:16Software Carbon Intensity metrics
- 24:44Resources and closing
related talks
42mJava in the Cloud with GraalVM
59mMaximizing performance with GraalVM
44mJava In The Cloud with GraalVM
49mSupercharge your Native Image applications
47mBring the action: using GraalVM in production
33mCloud-Friendly Applications with GraalVM
46mUnleash the power of your applications with Micronaut and GraalVM
55mUnleash the power of your applications with Micronaut and GraalVM