Benoit Daloze

That's a good point, a `benchmark-ips`-like warmup + mode (Ruby API) together with the builtin ability to compare multiple Rubies would be quite useful. #68 seems the main blocker for...

Has any in-process warmup been added to benchmark-driver? I had the impression it had but I can't find it now.

I'm taking another look today, because the benchmark-driver output is very confusing and leads many (almost all?) people to believe there is in-process warmup, when there is none. I'm documenting...

I'll try to give it a shot to implement in-proccess warmup in benchmark-driver soon, to help make progress here.

https://twitter.com/schwad_rb/status/1731446229878346119 for instance. I agree, yjit-bench is a much more relevant/representative benchmark suite and the default and other harnesses have in-process warmup there.

Thank you for asking. I think it's not good at least for TruffleRuby because TruffleRuby no-ops on `gem update --system` because it generally causes more problems than it solves and...

> It is recommended to prevent any `gem update --system` using `Gem.disable_system_update_message` Nice, I think I can use this in `rubygems/defaults/truffleruby.rb` so then there is no need to change anything...

https://github.com/ruby/ruby/pull/6935 was merged instead. I would prefer to deprecate and remove `rb_define_dummy_encoding()`, but I respect the meeting decision to instead limit to 256 encodings.

The built Rubies hardcode the PATH in which they were built, so they cannot be stored anywhere, so the toolcache path is fixed and cannot change. The only solution I...

I'll close this as not planned. As said above, if there is a clean enough PR adding it I'll consider it.