ruby.git - The Ruby Programming Language

Age	Commit message (Collapse)	Author
2023-03-06	Remove MJIT-specific benchmarks	Takashi Kokubun

2022-11-14	Rename --mjit-min-calls to --mjit-call-threshold (#6731)	Takashi Kokubun
	for consistency with YJIT Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
2022-08-21	Remove mjit_exec benchmarks	Takashi Kokubun
	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.
2022-08-21	Rename mjit_compile.c to mjit_compiler.c	Takashi Kokubun
	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.
2022-08-19	Rename mjit_exec to jit_exec (#6262)	Takashi Kokubun
	* Rename mjit_exec to jit_exec * Rename mjit_exec_slowpath to mjit_check_iseq * Remove mjit_exec references from comments Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
2021-12-13	Prepare for removing RubyVM::JIT (#5262)	Takashi Kokubun
	Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
2021-02-11	Do not run File.write while Ractors are running	Takashi Kokubun
	also make sure all local variables have the __bmdv_ prefix.
2021-02-10	Add a benchmark-driver runner for Ractor (#4172)	Takashi Kokubun
	* 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 Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
2021-01-13	Rename RubyVM::MJIT to RubyVM::JIT	Takashi Kokubun
	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]
2020-12-04	Guard all accesses to RubyVM::MJIT with defined?(RubyVM::MJIT) &&	Benoit Daloze
	* Otherwise those tests, etc cannot run on alternative Ruby implementations.
2020-06-22	Share warmup logic across MJIT benchmarks	Takashi Kokubun

2019-09-26	Reduce ISeq size of mjit_exec benchmark	Takashi Kokubun
	to avoid unwanted memory pressure
2019-09-26	Add special runner to benchmark mjit_exec	Takashi Kokubun
	I wanted to dynamically generate benchmark cases to test various number of methods. Thus I added a dedicated runner of benchmark-driver.
2019-07-02	Adjust memory_status.rb under the tool directory.	Hiroshi SHIBATA

2018-07-10	benchmark_driver/runner: add runners for metrics	k0kubun
	supported by legacy benchmark/driver.rb. benchmark/README.md: document them common.mk: update benchmark_driver to correct 0.0 output and to fix spacing format of `-o simple` and `-o markdown`. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63933 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-07-10	runner/size.rb: fix metric passed to output	k0kubun
	runner/peak.rb: ditto This is needed to make commands like `make -C .ruby-svn benchmark ITEM=erb OPTS="-r size -o simple"` succeed. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63932 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-07-10	benchmark: resurrect peak / size metrics	k0kubun
	by adding runner plugins for them. benchmark/lib/benchmark_driver/runner/peak.rb: added peak runner plugin benchmark/lib/benchmark_driver/runner/size.rb: added size runner plugin common.mk: allow using them benchmark/memory_wrapper.rb: deleted in favor of those runner plugins benchmark/README.md: document them git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63924 b2dd03c8-39d4-4d8f-98ff-823fe69b080e