this started earlier today in IRC, the idea was that now, that we are
having a denser memory layout in the vtables, we could simply reorder
the functions in the .eo files into groups that are often called next to
each other, that rises the chance that the Vtable nodes as well as the
chains are still in the cache.
After searching a bit for these groups, the below changed .eo files came
up. When a object is constructed, we call a lot parent set constructor
finalizer and provider find stuff. So moving these together seems
During rendering we also call a lot of gfx hints, which is also paying
off, our cache miss number goes down quite a bit.
cache misses averages: (Messured on a Dell XPS i7-7700HQ)
without this: 8945471 with this: 8014886
Depends on D11539