ruby/benchmark/vm_ivar_embedded_obj_init.yml

prelude: |
  class C
    def set_ivars
      @a = nil
      @b = nil
      @c = nil
    end
  end

  c = C.new
benchmark:
  vm_ivar_embedded_obj_init: |
    c.set_ivars
loop_count: 30000000
eagerly initialize ivar table when index is small enough When the inline cache is written, the iv table will contain an entry for the instance variable. If we get an inline cache hit, then we know the iv table must contain a value for the index written to the inline cache. If the index in the inline cache is larger than the list on the object, but smaller than the iv index table on the class, then we can just eagerly allocate the iv list to be the same size as the iv index table. This avoids duplicate work of checking frozen as well as looking up the index for the particular instance variable name. 2020-11-06 21:11:20 +03:00			`prelude: \|`
			`class C`
Fixes ivar benchmarks to not depend on object allocation Prior to this change, we were measuring object allocation as well as setting instance variables within ivar benchmarks. With this change, we now only measure setting instance variables within ivar benchmarks. 2022-07-15 17:12:51 +03:00			`def set_ivars`
eagerly initialize ivar table when index is small enough When the inline cache is written, the iv table will contain an entry for the instance variable. If we get an inline cache hit, then we know the iv table must contain a value for the index written to the inline cache. If the index in the inline cache is larger than the list on the object, but smaller than the iv index table on the class, then we can just eagerly allocate the iv list to be the same size as the iv index table. This avoids duplicate work of checking frozen as well as looking up the index for the particular instance variable name. 2020-11-06 21:11:20 +03:00			`@a = nil`
			`@b = nil`
			`@c = nil`
			`end`
			`end`
Fixes ivar benchmarks to not depend on object allocation Prior to this change, we were measuring object allocation as well as setting instance variables within ivar benchmarks. With this change, we now only measure setting instance variables within ivar benchmarks. 2022-07-15 17:12:51 +03:00
			`c = C.new`
eagerly initialize ivar table when index is small enough When the inline cache is written, the iv table will contain an entry for the instance variable. If we get an inline cache hit, then we know the iv table must contain a value for the index written to the inline cache. If the index in the inline cache is larger than the list on the object, but smaller than the iv index table on the class, then we can just eagerly allocate the iv list to be the same size as the iv index table. This avoids duplicate work of checking frozen as well as looking up the index for the particular instance variable name. 2020-11-06 21:11:20 +03:00			`benchmark:`
Added vm_ivar benchmark for initializing an embedded obj 2022-06-16 18:01:22 +03:00			`vm_ivar_embedded_obj_init: \|`
Fixes ivar benchmarks to not depend on object allocation Prior to this change, we were measuring object allocation as well as setting instance variables within ivar benchmarks. With this change, we now only measure setting instance variables within ivar benchmarks. 2022-07-15 17:12:51 +03:00			`c.set_ivars`
eagerly initialize ivar table when index is small enough When the inline cache is written, the iv table will contain an entry for the instance variable. If we get an inline cache hit, then we know the iv table must contain a value for the index written to the inline cache. If the index in the inline cache is larger than the list on the object, but smaller than the iv index table on the class, then we can just eagerly allocate the iv list to be the same size as the iv index table. This avoids duplicate work of checking frozen as well as looking up the index for the particular instance variable name. 2020-11-06 21:11:20 +03:00			`loop_count: 30000000`