ruby/benchmark/vm_fiber_switch.yml

prelude: |
  # based on benchmark for [ruby-core:65518] [Feature #10341] by Knut Franke
  fib = Fiber.new do
    loop { Fiber.yield }
  end
benchmark:
  vm_fiber_switch: |
    fib.resume
loop_count: 20000000
benchmark: convert bm_vm2_.rb to vm2_.yml This YAML transformation is needed to support whileloop2 time substituion by benchmark_driver.gem later. This commmit changes no benchmark behavior. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63892 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-07-08 18:35:22 +03:00			`prelude: \|`
			`# based on benchmark for [ruby-core:65518] [Feature #10341] by Knut Franke`
benchmark/vm2_*.yml: abstract away the while loop git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63896 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-07-08 20:03:23 +03:00			`fib = Fiber.new do`
			`loop { Fiber.yield }`
			`end`
benchmark: convert bm_vm2_.rb to vm2_.yml This YAML transformation is needed to support whileloop2 time substituion by benchmark_driver.gem later. This commmit changes no benchmark behavior. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63892 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-07-08 18:35:22 +03: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 07:37:42 +03:00			`vm_fiber_switch: \|`
benchmark/vm2_*.yml: abstract away the while loop git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63896 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-07-08 20:03:23 +03:00			`fib.resume`
Improved fiber benchmarks. Increase number of iterations. 2019-06-02 04:48:47 +03:00			`loop_count: 20000000`