diff options
| author | Takashi Kokubun <takashikkbn@gmail.com> | 2020-04-13 21:37:42 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-13 21:37:42 -0700 |
| commit | f883d6219e107554ebde5dff6d2f8383857f7518 (patch) | |
| tree | 295da84ed01841281ca7ed0510effa074def19b8 /benchmark/vm_gc_wb_obj_promoted.yml | |
| parent | 9fa24018b761d8902ad430ce604b174cf55062ab (diff) | |
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.
Notes
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
Diffstat (limited to 'benchmark/vm_gc_wb_obj_promoted.yml')
| -rw-r--r-- | benchmark/vm_gc_wb_obj_promoted.yml | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/benchmark/vm_gc_wb_obj_promoted.yml b/benchmark/vm_gc_wb_obj_promoted.yml new file mode 100644 index 0000000000..00a454ba72 --- /dev/null +++ b/benchmark/vm_gc_wb_obj_promoted.yml @@ -0,0 +1,17 @@ +prelude: | + class C + attr_accessor :foo + end + long_lived = C.new + + if RUBY_VERSION >= "2.2.0" + 3.times{ GC.start(full_mark: false, immediate_mark: true, immediate_sweep: true) } + elsif + GC.start + end + + short_lived = '' +benchmark: + vm_gc_wb_obj_promoted: | + long_lived.foo = short_lived # write barrier +loop_count: 30000000 |