ruby/benchmark/mjit_exec_vm2jt.yml

type: lib/benchmark_driver/runner/mjit_exec
num_methods: [1]
#num_methods: (1..100).to_a + [200, 300, 400, 500, 600, 700, 800, 900, 1000]
loop_count: 50000000
from_jit: false
to_jit: true
Stop relying on `make benchmark`'s `-I$(srcdir)/benchmark/lib` These days I don't use `make benchmark`. The YAML files should be executable with bare `benchmark-driver` CLI without passing `RUBYOPT=-Ibenchmark/lib`. 2020-06-22 10:17:09 +03:00			`type: lib/benchmark_driver/runner/mjit_exec`
Add special runner to benchmark mjit_exec I wanted to dynamically generate benchmark cases to test various number of methods. Thus I added a dedicated runner of benchmark-driver. 2019-09-26 06:57:43 +03:00			`num_methods: [1]`
Reduce ISeq size of mjit_exec benchmark to avoid unwanted memory pressure 2019-09-26 16:13:24 +03:00			`#num_methods: (1..100).to_a + [200, 300, 400, 500, 600, 700, 800, 900, 1000]`
			`loop_count: 50000000`
Add special runner to benchmark mjit_exec I wanted to dynamically generate benchmark cases to test various number of methods. Thus I added a dedicated runner of benchmark-driver. 2019-09-26 06:57:43 +03:00			`from_jit: false`
			`to_jit: true`