Главная
Study mode:
on
1
Intro
2
Goal of this talk
3
Chriss background
4
What is Twitter
5
Why run on Graal
6
Compilation issues
7
The fix
8
The crash
9
What is snippets
10
Time to bite the bullet
11
This never happened
12
This was an important part
13
Possible failure
14
Twoline fix
15
Compact Strings
16
Integral
17
Graphs
18
Memory Leak
19
Use CPU Time
20
CPU Utilization
21
Tweet Service
22
Escape Analysis
23
Money
24
Data centers
25
Cloud providers
26
Cost per CPU core
27
Amazon Google and Microsoft
28
Cost of 10k servers
29
What if we inline more
30
Tweak this
31
Second experiment
32
JIT compiler
33
Oracle JDK
34
Java Conferences
35
Summary
36
Hands Up
37
First Row
38
Use Cases
39
Inlining Parameter Tweak
40
Optimizations
41
IO
42
JVM
43
Enterprise Crawl
44
The Question
45
The Answer
Description:
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.

Twitter's Quest for a Wholly Graal Runtime

Scala Days Conferences
Add to list