Chrome won’t eat up RAM. The RawDraw function can already be turned on

Get real time updates directly on you device, subscribe now.

Chrome has introduced the RawDraw function, which reduces the load on the processor with the video card and reduces the consumption of RAM – at the moment it is available as a flag in the developer menu and is at an early stage of development. This was reported by Android Police.

When loading a page, the browser receives a so-called layer tree, which tells where and what information (text, images, etc.) needs to be displayed. Every time something happens on the screen (including the user’s scrolling of the page), the web browser needs to redraw the displayed data. To improve performance and reduce the consumption of system resources, browsers (at least on the Chromium engine) have long learned to split the page into a conditional grid with cells of approximately 256 × 256 pixels in order to update only the necessary areas, and not the entire page.

Visualizing Field Boundaries with Chromium Development Tools | Intel

However, on modern high-resolution displays, each such cell can take up to 10 MB of RAM – if there are many active elements on the page, and the user also uses several tabs in parallel, resource consumption becomes very significant. The RawDraw function is designed to change the rendering of a web page – with it the browser “does not allocate textures for each cell on the grid, but stores only drawing operations.” This reduces the load on the processor and the consumption of RAM.

You can enable RawDraw right now by activating the flag in the Chrome developer settings:

chrome:flags#enable-raw-draw

However, at the moment, the function is extremely unstable – apparently, it is only at the initial stage of development.

Get real time updates directly on you device, subscribe now.

Leave A Reply

Your email address will not be published.