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.
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.