On top of the tab rendering process, we get the GPU process which apparently has a hard time feeding the GPU all those moving lines and shapes. Taking into account that the scaling is different we can see that the CPU utilization during the Canvas demo practically doubled. Now let’s have the same chart for Chrome with GPU hardware acceleration turned on: Chrome: CPU Usage with Hardware Acceleration
The different colors indicate which Chrome sub-processes perform how much work. The four test phases are clearly visible. Let’s take a look at the CPU utilization of Chrome without GPU acceleration first: Chrome: CPU Usage without Hardware Acceleration For data collection and visualization I used our Windows performance monitoring product uberAgent for Splunk. The tests were run on a Lenovo W540 with an Intel HD Graphics 4600 GPU. 95m, Firefox 34.0.5, and Internet Explorer. I ran all three major browsers in their newest incarnations through the scenario outlined above: Chrome. Suffice to say that there are great differences between the browsers tested. While running these tests I deliberately ignored things like visual quality, framerates, etc.
Nobody seems to have measured how GPU acceleration affects CPU usage. Interestingly, facts to prove that are hard to find.
People generally seem to be happy about that – GPUs are super-efficient, the more work they do the fewer remains for the CPU, overall energy consumption is reduced and battery life increases. Chrome, Firefox, and Internet Explorer all have hardware acceleration turned on by default. Today, applications like Microsoft Office leverage the GPU, but even more so do web browsers. After slowly but steadily moving out of the 3D niche it has arrived in the mainstream.
0 kommentar(er)
