Slide 1

Slide 1 text

Takashi Kokubun @k0kubun Ruby 2.6 JIT

Slide 2

Slide 2 text

@k0kubun Takashi Kokubun / Arm Ruby Committer for JIT, ERB

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

Ruby 2.6

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

What's "JIT"?

Slide 10

Slide 10 text

JIT: Just In Time Compiler

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

History of Ruby implementation

Slide 13

Slide 13 text

def plus(a, b) a + b end + a b Parse Ruby 1.8 Traverse

Slide 14

Slide 14 text

def plus(a, b) a + b end + a b Compile Ruby 1.9~2.5 Interpret getlocal :a getlocal :b send :+

Slide 15

Slide 15 text

def plus(a, b) a + b end + a b JIT Ruby 2.6 (New!) Execute getlocal :a getlocal :b send :+ mov %rdi,%rdx mov %rsi,%rax add %rdx,%rax

Slide 16

Slide 16 text

How can we use it?

Slide 17

Slide 17 text

or ruby --jit ... RUBYOPT="--jit" rails s ...

Slide 18

Slide 18 text

Let's benchmark Ruby 2.6 JIT

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

https://gist.github.com/k0kubun/887b9567afa86b326556389ef00e4200

Slide 21

Slide 21 text

https://gist.github.com/k0kubun/887b9567afa86b326556389ef00e4200 Ruby 2.0: 34.3 Ruby 2.6: 86.7 2.53x faster

Slide 22

Slide 22 text

https://gist.github.com/k0kubun/887b9567afa86b326556389ef00e4200 Ruby 2.5: 48.3 Ruby 2.6: 86.7 1.80x faster

Slide 23

Slide 23 text

Achieved Ruby 3x2.5 !!!

Slide 24

Slide 24 text

How about other benchmarks?

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

JIT makes things slower?

Slide 28

Slide 28 text

Today's topic JIT performance characteristics

Slide 29

Slide 29 text

When does Ruby become slow on JIT?

Slide 30

Slide 30 text

1. When there are many JIT-ed methods

Slide 31

Slide 31 text

--jit-max-cache (default: 1000)

Slide 32

Slide 32 text

JIT by C compiler & dynamic loading

Slide 33

Slide 33 text

unused space code readonly data 1 method Heap

Slide 34

Slide 34 text

unused space code readonly data 1 method Heap 2MB (big) about 4KB ?KB

Slide 35

Slide 35 text

unused space code readonly data unused space code readonly data unused space code readonly data 3 methods Heap

Slide 36

Slide 36 text

unused space code readonly data unused space code readonly data unused space code readonly data L2, ... cache L1 cache Heap

Slide 37

Slide 37 text

unused space code readonly data unused space code readonly data unused space code readonly data L2, ... cache L1 cache Heap

Slide 38

Slide 38 text

unused space Heap code readonly data unused space code readonly data unused space code readonly data L2, ... cache L1 cache

Slide 39

Slide 39 text

2. When there are still methods to be JIT-ed

Slide 40

Slide 40 text

"JIT compaction"

Slide 41

Slide 41 text

unused space code readonly data unused space code readonly data unused space code readonly data When it reaches --jit-max-cache, it fires "JIT compaction"

Slide 42

Slide 42 text

unused space code readonly data unused space code readonly data unused space code readonly data unused space code code code readonly data readonly data readonly data

Slide 43

Slide 43 text

unused space code readonly data unused space code readonly data unused space code readonly data unused space code code code readonly data readonly data readonly data L2, ... cache

Slide 44

Slide 44 text

CPU/memory resources for C compiler

Slide 45

Slide 45 text

Locks on GC, waitpid, ...

Slide 46

Slide 46 text

3. When TracePoint is enabled (to be fixed after Ruby 2.6)

Slide 47

Slide 47 text

What's TracePoint? When is it enabled? • gem 'web-console' on your Rails application • byebug or binding.pry (with pry-byebug) • Measuring coverage

Slide 48

Slide 48 text

Summary: When JIT makes Ruby slow Optcarrot Rails 1. When there are many JIT-ed methods ✓ 2. When there are still methods to be JIT-ed (Is it a short benchmark?) ✓ 3. When TracePoint is enabled

Slide 49

Slide 49 text

What is made faster by JIT?

Slide 50

Slide 50 text

1. Almost all methods

Slide 51

Slide 51 text

def plus(a, b) a + b end Virtual Machine getlocal :a getlocal :b send :+ Program Counter Stack Pointer Computer Registers Instruction Pointer

Slide 52

Slide 52 text

def plus(a, b) a + b end Virtual Machine getlocal :a getlocal :b send :+ Program Counter Stack Pointer Computer JIT Instruction Pointer Registers mov %rdi,%rdx mov %rsi,%rax add %rdx,%rax

Slide 53

Slide 53 text

2. Basic operators on core classes

Slide 54

Slide 54 text

VM-optimized methods Integer, Float +, -, *, /, % Array +, <<, [], []=, empty?, size, length, min, max Hash [], []=, empty?, size, length String +, <<, =~, empty?, size, length, succ common !, !=, ==, <, >, <=, >=

Slide 55

Slide 55 text

def three 1 + 2 end putobject 1 putobject 2 send :+ JIT mov $0x3,%eax retq Method inlining on JIT

Slide 56

Slide 56 text

3. Calling Ruby method

Slide 57

Slide 57 text

Method dispatch on Ruby VM foo.bar

Slide 58

Slide 58 text

Method dispatch on Ruby VM foo.bar Method search (slow)

Slide 59

Slide 59 text

Method dispatch on Ruby VM foo.bar Method search (slow) Ruby method C function attr_reader alias Method entry Foo#bar

Slide 60

Slide 60 text

Method dispatch on Ruby VM foo.bar Method search (slow) Verify cache Ruby method C function attr_reader alias Method entry Foo#bar has cache

Slide 61

Slide 61 text

Method dispatch on Ruby VM foo.bar Method search (slow) Verify cache Ruby method C function attr_reader alias Method entry Foo#bar has cache redefined?

Slide 62

Slide 62 text

Method dispatch on Ruby VM foo.bar Method search (slow) Verify cache Ruby method C function attr_reader alias Method entry Foo#bar has cache redefined?

Slide 63

Slide 63 text

Method dispatch on JIT foo.bar Verify cache Ruby method Method entry Foo#bar has cache Cancel JIT! Less branches Less memory access redefined? some inlining

Slide 64

Slide 64 text

4. Instance variable access

Slide 65

Slide 65 text

Reading instance variable on VM @foo

Slide 66

Slide 66 text

Reading instance variable on VM @foo Search index (many branches, slow)

Slide 67

Slide 67 text

Reading instance variable on VM @foo Search index (many branches, slow) self.class. instance_variables[index = 2]

Slide 68

Slide 68 text

Reading instance variable on VM Search index (many branches, slow) self.class. instance_variables[index = 2] @foo has cache Verify cache

Slide 69

Slide 69 text

Reading instance variable on VM Search index (many branches, slow) self.class. instance_variables[index = 2] @foo different class? has cache Verify cache

Slide 70

Slide 70 text

Reading instance variable on VM Search index (many branches, slow) self.class. instance_variables[index = 2] @foo different class? has cache Verify cache

Slide 71

Slide 71 text

Reading instance variable on JIT self.class. instance_variables[2] @foo different class? has cache Verify cache Cancel JIT! inlined index Less branches Less memory access

Slide 72

Slide 72 text

Summary: When JIT makes Ruby fast Optcarrot Rails 1. Almost all methods ✓ ✓ 2. Basic operators on core classes ✓ 3. Calling Ruby method ✓ ✓ 4. Instance variable access ✓ ?

Slide 73

Slide 73 text

Future of Ruby's JIT

Slide 74

Slide 74 text

Will Ruby 2.6 be fast only on Optcarrot?

Slide 75

Slide 75 text

Future idea (not for 2.6) • Stack allocation of objects - That requires "escape analysis" (not easy) - We haven't estimated its possible impact yet

Slide 76

Slide 76 text

Some rooms for improvements in 2.6 (!?) • Change heuristics to trigger/compact JIT • Profile-guided optimization • Method inlining

Slide 77

Slide 77 text

How can we experiment them? Benchmark!

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

Create a benchmark for Ruby 3x3?

Slide 81

Slide 81 text

benchmark_driver.gem

Slide 82

Slide 82 text

No content

Slide 83

Slide 83 text

No content

Slide 84

Slide 84 text

No content

Slide 85

Slide 85 text

No content

Slide 86

Slide 86 text

Conclusion • Ruby 2.6.0-preview3 JIT is still early days - Small --jit-max-cache might be an option for now • We still have chance to make Ruby 2.6.0 better - Benchmarks are wanted!!!