A experimental sampling-based profiler for Ruby 3.3+.
Run your Ruby program through pf2 serve.
Wait a while until Pf2 collects profiles (or until the target program exits), then open the displayed link for visualization.
$ pf2 serve -- ruby target.rb
[Pf2] Listening on localhost:51502.
[Pf2] Open https://profiler.firefox.com/from-url/http%3A%2F%2Flocalhost%3A51502%2Fprofile for visualization.
I'm the target program!Pf2 will collect samples every 10 ms of wall time by default.
# Threads in `threads` will be tracked
Pf2.start(threads: [Thread.current])
your_code_here
# Stop profiling and save the profile for visualization
profile = Pf2.stop
File.write("my_program.pf2profile", profile)Alternatively, you may provide a code block to profile.
profile = Pf2.profile do
your_code_here() # will be profiled
Thread.new { threaded_code() } # will also be profiled
end
# Save the profile for visualization
File.write("my_program.pf2profile", profile)Profiles can be visualized using the Firefox Profiler.
$ pf2 report -o report.json my_program.pf2profilePf2 accepts the following configuration keys:
Pf2.start(
interval_ms: 9, # Integer: The sampling interval in milliseconds (default: 9)
time_mode: :cpu, # `:cpu` or `:wall`: The sampling timer's mode
# (default: `:cpu` for SignalScheduler, `:wall` for TimerThreadScheduler)
threads: [th1, th2], # `Array<Thread>` | `:all`: A list of Ruby Threads to be tracked.
# When `:all` or unspecified, Pf2 will track all active Threads.
)While Pf2 aims to be non-disturbulent as much as possible, a small overhead still is incured.
(TBD)
Pf2 cannot properly track program activity in some known cases. I'm working to remove these limtations, so stay tuned.
RUBY_MN_THREADS) is enabledPf2 is a sampling profiler. 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_profile_thread_frames() API for sampling. When to do so is controlled by Schedulers, described in the following section.
Schedulers determine when to execute sample collection, based on configuration (time mode and interval). Pf2 has two schedulers available.
The first 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(2). This leaves the actual time-keeping to the OS, which is capable of tracking accurate per-thread CPU time usage.
When the specified interval has arrived (the timer has expired), the OS delivers us a SIGALRM (note: Unlike setitimer(2), timer_create(2) 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).
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 infinite loop will be run inside. After sleep(2)-ing for the specified 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 profiling.
The gem is available as open source under the terms of the MIT License.