Closed casperisfine closed 1 year ago
Ref: https://bugs.ruby-lang.org/issues/19443
Recent glibc no longer cache the PID, so every call to Process.pid end up emitting a syscall which as an impact on performance.
glibc
Process.pid
Ruby 3.3 may or may not do PID caching, in the meantime we can implement our own caching in Ruby 3.1+ using the Process._fork callback.
Process._fork
FYI: @dalehamel
Ref: https://bugs.ruby-lang.org/issues/19443
Recent
glibc
no longer cache the PID, so every call toProcess.pid
end up emitting a syscall which as an impact on performance.Ruby 3.3 may or may not do PID caching, in the meantime we can implement our own caching in Ruby 3.1+ using the
Process._fork
callback.FYI: @dalehamel