0
Files
src/cc
danakj@chromium.org 4f4d8b5349 cc: Turn overdraw metrics on only when about:tracing is recording.
Now that we're in chromium, we can tell if about:tracing is enabled ot not!
Turn on overdraw metrics, and their expensive computations, only when
about:tracing is turned on.

When we do turn them on, we don't want the performance characteristics of
the system to suddenly change, or the tracing is not very meaningful! So, we
track the number of pixels read, instead of written, for overdraw (which
should mostly be the same with the new rasterScale feature). This
computation is very cheap compared to the old one.

TBR=jamesr
BUG=119126
Relanding: https://codereview.chromium.org/11293143/

Review URL: https://codereview.chromium.org/11312129

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166521 0039d316-1c4b-4281-b951-d872f2087c98
2012-11-07 21:20:33 +00:00
..
2012-11-02 21:06:20 +00:00
2012-11-06 05:53:00 +00:00
2012-11-06 05:53:00 +00:00
2012-11-06 05:53:00 +00:00
2012-11-06 05:53:00 +00:00
2012-11-03 21:10:11 +00:00
2012-11-02 12:08:11 +00:00
2012-10-31 22:48:14 +00:00
2012-11-02 21:06:20 +00:00
2012-11-02 21:06:20 +00:00

This is the chromium compositor implementation.

Notes about the component=shared_library build:
Because the compositor currently depends on non-exported symbols from inside
WebKit, in the shared library build the cc library links into WebKit.dll.
The unit tests don't currently work at all in the component build.