3 ms·
I'm not sure if you are referring to a particular optimization, but speaking of https://twitter.com/bmeurer/status/834677090381348865 https://twitter.com/bmeur
by bmeurer 10y ago
I'm not sure if you are referring to a particular optimization, but speaking of
https://twitter.com/bmeurer/status/834677090381348865 https://twitter.com/bmeurer/status/834677090381348865
and
https://twitter.com/bmeurer/status/834668611180625921 https://twitter.com/bmeurer/status/834668611180625921
the "Bazinga!" event in both cases refers to two very specific fixes that addressed deoptimization loops in TurboFan. The more interesting steady increase in performance is due to long-term real-world performance work, especially in the area of data-driven ICs (inline caches) and function context specialization.
We will follow up with more details about Ignition and TurboFan, and the whole new code generation architecture soon.
- fmap 10y agoYes, that's what I had in mind. Another thing I seem to recall is that Turbofan used to be a lot slower than Crankshaft and spend a lot of its time in scheduling and register allocation. Has this changed recently? In any case, I'm looking forward to the more in depth post. :)