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.
So far the feedback from Node.js users/developers indicates that the --future configuration is a net win. There are some cases where performance degrades, and we are actively working on those. Instructions how to test-drive --future with Node.js can be found here: https://medium.com/@bmeurer/help-us-test-the-future-of-node-...
https://twitter.com/bmeurer/status/834677090381348865
and
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.