delta/ruby.git/benchmark/lib, branch ruby_3_2

Rename --mjit-min-calls to --mjit-call-threshold (#6731)

2022-11-15T07:38:52+00:00

for consistency with YJIT

Remove mjit_exec benchmarks

2022-08-21T18:35:40+00:00

Now that mjit_exec doesn't exist, those files feel old. I'll probably
change how I benchmark it when I add benchmarks for it again.

Rename mjit_compile.c to mjit_compiler.c

2022-08-21T18:33:06+00:00

I'm planning to introduce mjit_compiler.rb, and I want to make this
consistent with it. Consistency with compile.c doesn't seem important
for MJIT anyway.

Rename mjit_exec to jit_exec (#6262)

2022-08-20T06:57:17+00:00

* Rename mjit_exec to jit_exec

* Rename mjit_exec_slowpath to mjit_check_iseq

* Remove mjit_exec references from comments

Prepare for removing RubyVM::JIT (#5262)

2021-12-14T07:07:46+00:00

Do not run File.write while Ractors are running

2021-02-11T08:25:46+00:00

also make sure all local variables have the __bmdv_ prefix.

Add a benchmark-driver runner for Ractor (#4172)

2021-02-11T05:24:25+00:00

* Add a benchmark-driver runner for Ractor

* Process.clock_gettime(Process:CLOCK_MONOTONIC) could be slow

in Ruby 3.0 Ractor

* Fetching Time could also be slow

* Fix a comment

* Assert overriding a private method

Rename RubyVM::MJIT to RubyVM::JIT

2021-01-14T06:46:51+00:00

because the name "MJIT" is an internal code name, it's inconsistent with
--jit while they are related to each other, and I want to discourage future
JIT implementation-specific (e.g. MJIT-specific) APIs by this rename.

[Feature #17490]

Guard all accesses to RubyVM::MJIT with defined?(RubyVM::MJIT) &&

2020-12-04T15:45:54+00:00

* Otherwise those tests, etc cannot run on alternative Ruby implementations.

Share warmup logic across MJIT benchmarks

2020-06-22T07:54:27+00:00