今年のRubyKaigiはProfiler Year🤘

Slide 1

Slide 1 text

@osyoyu | 2024/4/25 RubyKaigi 2024ࣄલษڧձ ࠓ೥ͷRubyKaigi͸Profiler Year🤘

Slide 11

Slide 11 text

Pf2 ͷ࢓૊Έ ΈΜͳڵຯ͋ΔΑͶ Sampling Pf2 is a sampling pro fi ler. This means that Pf2 collects samples of program execution periodically, instead of tracing every action (e.g. method invocations and returns). Pf2 uses the rb_pro fi le_thread_frames() API for sampling. When to do so is controlled by Schedulers, described in the following section. Schedulers Schedulers determine when to execute sample collection, based on con fi guration (time mode and interval). Pf2 has two schedulers available. SignalScheduler (Linux-only) The fi rst is the SignalScheduler, based on POSIX timers. Pf2 will use this scheduler when possible. SignalScheduler creates a POSIX timer for each Ruby Thread (the underlying pthread to be more accurate) using timer_create(3). This leaves the actual time-keeping to the OS, which is capable of tracking accurate per-thread CPU time usage. When the speci fi ed interval has arrived (the timer has expired), the OS delivers us a SIGALRM (note: Unlike setitimer(2), timer_create(3) allows us to choose which signal to be delivered, and Pf2 uses SIGALRM regardless of time mode). This is why the scheduler is named SignalScheduler. Signals are directed to Ruby Threads' underlying pthread, effectively "pausing" the Thread's activity. This routing is done using SIGEV_THREAD_ID, which is a Linux-only feature. Sample collection is done in the signal handler, which is expected to be more accurate, capturing the paused Thread's activity. This scheduler heavily relies on Ruby's 1:N Thread model (1 Ruby Threads is strongly tied to a native pthread). It will not work properly in MaNy (RUBY_MN_THREADS=1). TimerThreadScheduler Another scheduler is the TimerThreadScheduler, which maintains a time-keeping thread by itself. A new native thread (pthread on Linux/macOS) will be created, and an in fi nite loop will be run inside. After sleep(2)-ing for the speci fi ed interval time, sampling will be queued using Ruby's Postponed Job API. This scheduler is wall-time only, and does not support CPU-time based pro fi ling.

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Slide 30

Slide 30 text

Slide 31

Slide 31 text

Slide 32

Slide 32 text

Slide 33

Slide 33 text

Slide 34

Slide 34 text

Slide 35

Slide 35 text

Slide 36

Slide 36 text

Slide 37

Slide 37 text

Slide 38

Slide 38 text

Slide 39

Slide 39 text

Slide 40

Slide 40 text