Skip to content
0:00 / 0:00

#graalvm#jit#aot

Java Performance Myths: JIT vs AOT, GraalVM, Compilers – Thomas Wuerthinger | The Marco Show

IntelliJ IDEA, a JetBrains IDE

135K subscribers • 10 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Thomas Wuerthinger, Founder and Project Lead of GraalVM
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

8.8K views8 months ago1 recommendation

Programming languagesSystems programmingJava and the JVMCompilers and interpretersPerformance and optimization

Thomas Wuerthinger discusses GraalVM, native compilation, and the performance trade-offs between JIT and AOT compilers.

GraalVM promises faster startup, lower memory usage, and predictable performance — but when does it actually beat the JVM as we know it? In this episode of The Marco Show, Marco talks with Thomas Wuerthinger, Founder and Project Lead of GraalVM and Vice President at Oracle, about compilers, Java performance, native images, polyglot runtimes, and what really matters when software runs at scale. Thomas shares why rebuilding runtimes for every language is a waste of engineering effort, how GraalVM grew from a research project into a production-grade platform, and why Native Image unexpectedly became its most impactful feature. They also unpack the One Billion Row Challenge, performance myths around JIT vs AOT, branch misprediction failures, cloud economics, Python and JavaScript runtimes, and the role of AI in compiler development. This episode is a deep dive into how modern runtimes actually work — and how performance decisions play out in the real world. 🎁 Giveaway How many lines of open-source code are maintained across GraalVM and its related language projects? Drop your guess in the comments 👇 Timestamps – Intro – Meet Thomas Wuerthinger & what GraalVM really is – Why duplicating language runtimes is a waste – How GraalVM started at Sun Microsystems Labs – Writing an interpreter and getting a JIT “for free” – Going open source and finding real users – Why Native Image took off – From research project to real product – Native Image, Spring, Quarkus, and Java in the cloud – Why JIT performance can be unpredictable – When JIT still makes sense – Python, JavaScript, and polyglot runtimes – Using AI in compilers and testing – The One Billion Row Challenge – Branch misprediction and performance surprises – How to think about performance optimization – Giveaway question – Rapid fire and wrap-up Follow Thomas: linkedin.com/in/thomaswue/ Follow The Marco Show: instagram.com/themarco.show Join us: Website: jb.gg/website Blog: jb.gg/blog X: twitter.com/intellijidea Bluesky: bsky.app/profile/intellijidea.com LinkedIn: linkedin.com/showcase/intellijidea Facebook: facebook.com/IntelliJIDEA/ Download IntelliJ IDEA: jb.gg/download-intellij-idea

Why it's here

1 person recommends this

What people say. Recommended for its deep dive into Java performance and the JIT versus AOT debate.

u/mttdin r/Compilers • Recommends

"I would recommend JIT only if you absolutely have to use it" - The Future of Java: GraalVM, Native Compilation, Performance – Thomas Wuerthinger The Future of Java: GraalVM, Native Compilation, Performance – Thomas Wuerthinger | The Marco Show: link to this video (about 35 minutes in) > I mean the most obvious benefits to people was the startup. That's the thing that of course in nowadays social media-driven world was giving us the most viral content because you have a Java app and suddenly it starts in 5 milliseconds. Okay. A full Java server with Micronaut. So that's the number one benefit and that's why native image is used a lot in serverless environments for example where this fast startup is s…