Yes, this ticket is about sampling profilers. Sorry for the confusion. byroot (Jean Boussier) wrote in #note-11: > Which is an interesting choice, because maybe it's my bias, but I find that CPU-time profiling is really not as common...osyoyu (Daisuke Aritomo)
Eregon (Benoit Daloze) wrote in #note-6: > > I am rather doubtful that CRuby/JRuby/TruffleRuby can share any profiler implementation at all. > ... "Profiler implementation" meant (1) the sampling backend and (2) what information would ...osyoyu (Daisuke Aritomo)
Thank you for your comments and input! Eregon (Benoit Daloze) wrote in #note-4: > The API should not be under RubyVM, that's CRuby-specific `RubyVM` being CRuby-specific is actually the exact reason I choosed the place to locate a...osyoyu (Daisuke Aritomo)
> Any CPU timing in Ruby must also consider JIT improvements over time, and be able to decode things like inlined method calls so that the reported execution time is associated with the correct body of code. Yes, ZJIT probabaly would ...osyoyu (Daisuke Aritomo)
Modern CRuby workloads can consume CPU concurrently across multiple native threads, especially with multiple Ractors and C exts which release the GVL. I'd like to propose the idea of integrating a built-in CPU-time profiler CRuby to enab...osyoyu (Daisuke Aritomo)
Thank you for the summary! I'll open a separate ticket for auto-adjusting `RUBY_MAX_CPU`. Come to think of it, `RUBY_MAX_CPU` may have different requirements from `Etc.nprocessors` (defaulting to max # of processors may be suboptimal...osyoyu (Daisuke Aritomo)
It'd be nice if `RUBY_MAX_CPU` would be autoconfigured based on this, just like Go 1.25 `GOMAXPROCS`. Its default value is currently fixed to 8, but not many cloud containers have 8 cores worth of processors. https://github.com/ruby/...osyoyu (Daisuke Aritomo)
@eregon I'm not sure I fully understand your point, but conceptually your code should raise an `Ractor::IsolationError` by accessing a unshareable, mutable variable `a`. My proposal's intent was to preserve `self` while making the proc s...osyoyu (Daisuke Aritomo)
I have discovered that this issue reproduces when Gemfile contains a gem referred by `path:` or `git:`. Such Gemfiles are pretty much common in real-world applications including Rails, which use in-house Gems and libraries, like this: ...osyoyu (Daisuke Aritomo)
osyoyu (Daisuke Aritomo)11:33 AM Ruby Feature #21950: Add a built-in CPU-time profiler