diff options
| author | tapted <tapted@chromium.org> | 2015-12-02 19:00:38 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-12-03 03:01:25 +0000 |
| commit | 859410a5e85488c0b79de51814351f30cf2814a5 (patch) | |
| tree | 5428100492d53b688785069b84a69cd485b6ea94 /third_party/WebKit/Source/modules/webgl/EXTShaderTextureLOD.h | |
| parent | d4f917bdea72d448956cf1190a1398f302a93c3b (diff) | |
| download | chromium_src-859410a5e85488c0b79de51814351f30cf2814a5.zip chromium_src-859410a5e85488c0b79de51814351f30cf2814a5.tar.gz chromium_src-859410a5e85488c0b79de51814351f30cf2814a5.tar.bz2 | |
Paint tab-loading throbbers into a ui::Layer (reland).
In views browsers, updating the tab loading throbber currently requires
a repaint that starts at the BrowserView and trickles the damage
rectangle down until it reaches the favicon area. This uses a lot of CPU
and energy: about 11 watts above idle on a MacBook Pro (and significant
CPU on Linux) for a single "waiting" spinner.
Giving the throbber a layer allows the repaint to be isolated, with
compositing done on the GPU. This brings total energy usage down to
about 2.5 watts above idle.
Plots at http://crbug.com/391646#c44
Previously reviewed in https://codereview.chromium.org/1393193002/.
Landed but reverted since it tickled a pre-existing lifetime issue,
now fixed.
BUG=391646
TEST=Spinners should look and behave the same, but use less energy/CPU.
Review URL: https://codereview.chromium.org/1477713002
Cr-Commit-Position: refs/heads/master@{#362878}
Diffstat (limited to 'third_party/WebKit/Source/modules/webgl/EXTShaderTextureLOD.h')
0 files changed, 0 insertions, 0 deletions