Chrome 91 is 23% faster with these changes

Chrome 91 is now available in a stable phase since last week. The new ChromeOS offers a handful of new features. Everything is taken care of from major visual controls to minor changes like enhanced one-time password autofill service. Apart from these features, the new channel also drives some under the hood performance improvement, making it 23% faster than the predecessor.

Must see: Download latest wallpapers by Google Chrome OS here

The “Under the hood” changes mentioned above make the new Chrome channel faster and more efficient. Let’s take a look at these changes.

• Google executed Fast JavaScript, which is an “important component” for a fast browsing experience. In Chrome 91, the JavaScript is handled by the V8 engine. It brings off “over 78 years’ worth of JavaScript code on a daily basis,” says Google.
• Google has made some improvements to the V8 engine that boosts the performance at a significant rate. To be more precise, Google has kicked off “a new Sparkplug compiler and short built-in calls”. This apparently saves “over 17 years” of CPU time for Chrome users each day.

Back in May 2017, Google released a two-tier compiler system in the V8 engine for JavaScript execution in Chrome. The system consisted of Ignition and Turbofan. The components are responsible for quickly starting the JavaScript and optimizing the code for maximum performance respectively.

Turbofan works to generate high-performance machine codes by depending on the information gathered during JavaScript execution. Ultimately, this process results in a slower start-up and slow browsing experience than Ignition.

The latest engine is a new JavaScript compiler that fills the gap between these two phases. It is faster in generating high-performance codes as it does not depends on information gathered while executing the JavaScript for generating native machine codes.

On the other hand, in order to avoid indirect jumps when the calling function is active, the V8 engine is enabled to optimize the location in memory of generated code. Short built-in calls handle all the common routines. “When a CPU-specific code is generated from JavaScript, the V8 engine lays that code out in memory” explains Thomas Nattestad, Chrome Product Manager.

He further writes, “calling functions that are further away from your generated code can cause CPU-internal optimizations to fail.” The built-in functions are copied into the same memory region as the generated code to avoid optimization failures.