This website requires JavaScript.
Explore
Help
Sign in
kotovalexarian-likes-github
/
ruby--ruby
Watch
1
Star
0
Fork
You've already forked ruby--ruby
0
mirror of
https://github.com/ruby/ruby.git
synced
2022-11-09 12:17:21 -05:00
Code
Releases
Activity
ff43ecc0c1
ruby--ruby
/
benchmark
/
vm_simplereturn.yml
8 lines
91 B
YAML
Raw
Normal View
History
Unescape
Escape
benchmark/vm1_*.yml: abstract away the while loop benchmark/driver.rb had removed the cost for while loop in benchmark/bm_vm1_*.rb, and benchmark_driver.gem can achieve the same thing with `loop_count`. But unfortunately current benchmark_driver.gem can't solve it only for vm1_yield.yml... git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63893 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-07-08 12:28:34 -04:00
prelude
:
|
def m
return 1
end
benchmark: convert bm_vm1_*.rb to vm1_*.yml This YAML transformation is needed to support whileloop time substituion by benchmark_driver.gem later. This commmit changes no benchmark behavior. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63891 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-07-08 11:12:24 -04:00
benchmark
:
Unify vm benchmark prefixes to vm_ (#3028) The vm1_ prefix and vm2_ had had special meaning until 820ad9cb1d72d0897b73dae282df3793814b27e8 and 12068aa4e980ab32a0438408a519030e65dabf5e. AFAIK there's no special meaning in vm3_ prefix. As they have confused people (like "In `benchmark` what is difference between `vm1_`, `vm2_` and `vm3_`"), I'd like to remove the obsoleted prefix as we obviated that two years ago.
2020-04-14 00:37:42 -04:00
vm_simplereturn
:
m
benchmark/vm1_*.yml: abstract away the while loop benchmark/driver.rb had removed the cost for while loop in benchmark/bm_vm1_*.rb, and benchmark_driver.gem can achieve the same thing with `loop_count`. But unfortunately current benchmark_driver.gem can't solve it only for vm1_yield.yml... git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63893 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-07-08 12:28:34 -04:00
loop_count
:
30000000
Copy permalink