This document will focus on the most advanced architecture at the time of writing, which is not the shipping configuration on all platforms. Lastly, before we begin, a big disclaimer : the Chrome graphics stack has evolved substantially over the last several years. Parallelism between the CPU and GPU, which can operate at the same time to create an efficient graphics pipeline. The hardware is designed specifically for these types of workloads.Įxpensive readbacks aren’t necessary for content already on the GPU (such as accelerated video, Canvas2D, or WebGL). The benefits of hardware compositing come in three flavors:Ĭompositing page layers on the GPU can achieve far better efficiency than the CPU (both in terms of speed and power draw) in drawing and compositing operations that involve large numbers of pixels. Using the GPU to composite the contents of a web page can result in very significant speedups. With capable GPUs now an integral part of even the smallest of devices, attention has turned on finding ways to more effectively use this underlying hardware to achieve better performance and power savings. Traditionally, web browsers relied entirely on the CPU to render web page content. This document provides background and details on the implementation of hardware-accelerated compositing in Chrome. RenderObject to LayoutObject, RenderLayer to PaintLayer). Note also that some class names may have changed (e.g. Updated May 2014 This code is changing due to Slimming Paint and thus there may be large changes in the future. Tom Wiltzius, Vangelis Kokkevis & the Chrome Graphics team

What is gpu process in chrome