The problem is, 5 is a prime number. So cache mechanisms of any size cannot store this struct efficiently. Most notably, CPUs have been equipped with data caches since their mid age; Ruby's objects do not suit there. That does not always mean a breakage but significant slowdown is happening. Today I'd like to propose a fix around this; to make objects power-of-two sized. What I did was to make obj
![[Feature #9362] Minimize cache misshit to gain optimal speed by shyouhei · Pull Request #495 · ruby/ruby](https://cdn-ak-scissors.b.st-hatena.com/image/square/d53c5b30347ee6708a11972f4a90ce005298f56e/backend=imagemagick;height=288;version=1;width=512/https%3A%2F%2Fproxy.goincop1.workers.dev%3A443%2Fhttps%2Fopengraph.githubassets.com%2F5275f31cec9bc29e9f759c98384b332618821dbbd2875023846afeede45f038e%2Fruby%2Fruby%2Fpull%2F495)
