Twitter's Quest for a Wholly Graal Runtime

Explore Twitter's journey towards implementing the Graal runtime in this 50-minute conference talk from Scala Days New York 2018. Delve into the challenges faced by Twitter's engineering team, including compilation issues, crashes, and memory leaks. Learn about the innovative solutions developed, such as the two-line fix and compact strings. Examine the impact of these optimizations on CPU utilization, tweet service performance, and data center costs. Gain insights into the potential benefits of increased inlining and JIT compiler tweaks. Discover how Twitter's quest for improved runtime efficiency could lead to significant cost savings across thousands of servers. Understand the broader implications for Java development and enterprise-scale applications.

Intro
Goal of this talk
Chriss background
What is Twitter
Why run on Graal
Compilation issues
The fix
The crash
What is snippets
Time to bite the bullet
This never happened
This was an important part
Possible failure
Twoline fix
Compact Strings
Integral
Graphs
Memory Leak
Use CPU Time
CPU Utilization
Tweet Service
Escape Analysis
Money
Data centers
Cloud providers
Cost per CPU core
Amazon Google and Microsoft
Cost of 10k servers
What if we inline more
Tweak this
Second experiment
JIT compiler
Oracle JDK
Java Conferences
Summary
Hands Up
First Row
Use Cases
Inlining Parameter Tweak
Optimizations
IO
JVM
Enterprise Crawl
The Question
The Answer