Google News Productivity

Google Optimizes Chrome By Rescheduling Javascript Timers In Beta Version

Share on Facebook
Tweet about this on TwitterShare on Google+Share on StumbleUponShare on LinkedInPin on PinterestShare on Reddit

Google Chrome can easily be called one of the most snappiest browsers around. And Google is constantly improving the browser for better user experience and speed. In another such development, the new version of Chrome Beta is further optimised by rescheduling the Javascript timers (getting to what does it mean in a moment..!) being used in the scheduling process when the page is being loaded.

The announcement came in via a blog post by Alex Clarke, Software Engineer and Timer Tamer .

The latest change can be seen as further development of the scheduler which was incorporated into Chrome in March this year and is basically geared towards providing maximum speed of rendering, targeted at as high as 69 frames per second.

When a user interacts with a web page, after the page is loaded, there are various functions going on or to be done in the background. If a user then further clicks on any link of that web page, that task (rendering a frame) used to go to the end of that list of functions to be performed and the amount of time taken by the browser to paint the different frame (i.e opening that link on page) was higher. This was resolved by incorporating a scheduler which essentially prioritizes the less important tasks in the list by placing them in the idle time between rendering frame, thus providing a higher response speed to the user.

Now this frame rate of web browser can also be affected by the wrong execution of JavaScript timers. Javascript timers enable web developers to write codes that check in on a web page periodically by using APIs such as setTimeout.

Advanced developers can use it to schedule their code to run at appropriate time but quite often, they do not have the full information to schedule it at right time. This means that the code can be placed in the queue of tasks to be executed and can block high priority tasks like input or rendering, thereby slowing down the speed of browser for the user. Thus Javascript timers executing at the wrong time can also affect the frame rate and in the latest beta version of Chrome, their execution has been optimized.

So in the new version, when the user taps the page, they often interact with it again immediately or Chrome needs to re-render part of the screen. The scheduler now delays impending Javascript timers after a tap in anticipation of these tasks, allowing better scheduling of many web pages and according to the blog post, it has resulted into a 50% input latency improvement on websites that use timers heavily.

There is no announcement as to when would this feature come in the stable version of Chrome and as for now, it comes by default in the beta version.


[email protected]

Add Comment

Click here to post a comment

Your email address will not be published. Required fields are marked *