ruby--ruby/benchmark/vm_attr_ivar.yml

prelude: |
  class C
    attr_reader :a, :b
    def initialize
      @a = nil
      @b = nil
    end
  end
  obj = C.new
benchmark:
  vm_attr_ivar: |
    j = obj.a
    k = obj.b
loop_count: 30000000
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: \|`
			`class C`
			`attr_reader :a, :b`
			`def initialize`
			`@a = nil`
			`@b = nil`
			`end`
			`end`
			`obj = C.new`
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_attr_ivar: \|`
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			`j = obj.a`
			`k = obj.b`
			`loop_count: 30000000`