More

    Chrome 91 offers 23% faster performance for these changes

    - Advertisement -

    Google recently rolled out Chrome 91 on a stable channel. The update introduced several changes, including redesigned form controls, support for default desktop mode on large screen devices, file system access API improvements, and more.

    The update brought several performance improvements, and Google has now revealed that the latest update has made Chrome 23% faster than the previous release.

    In a recent post on the Chromium blog, Chrome Product Managing Director Thomas Nattestad revealed that “Chrome 91 is now up to 23% faster with the launch of a new Sparkplug compiler and short built-in calls, saving over 17 years of our users’ CPU time each day!” 

    - Advertisement -

    The post explains that SparkPlug is a new JavaScript compiler “fills the gap between needing to start executing quickly and optimizing the code for maximum performance.”On the other hand, short built-in calls optimize “wherein memory we put generated code to avoid indirect jumps when calling functions.”

    find in page chrome 91 3 1 1

    Chrome’s V8 engine has multiple compilers that trade-off different steps in different steps to execute JavaScript. The new SparkPlug compiler maintains a balance between the engine’s two-tiered compiler system – ignition and turbofan – to generate native machine code without relying on information collected while executing JavaScript code. Due to this, it “starts executing quickly while still generating relatively fast code,” thereby improving performance.

    Short bulletins are a new mechanism that helps the V8 engine to optimize position in memory of generated code. “When V8 generates CPU-specific code from JavaScript, it lays that code out in memory. This generated code will frequently call built-in functions, which are small snippets of code for handling common routines –everything from basic operations like adding two variables to full-fledged functions in the JavaScript standard library. For some CPUs, calling functions further away from your generated code can cause CPU-internal optimizations (such as branch prediction logic) to fail. The fix for this is to copy the built-in functions into the same memory region as the generated code,” the post adds. It further notes that this change will improve the functionality of Chrome on the Apple M1 chip.

    - Advertisement -

    Get in Touch

    LEAVE A REPLY

    Please enter your comment!
    Please enter your name here

    Latest Posts