Clamp texture queries to sane values.

Clamp texture queries to sane values.

Some device's concept of time might be off.
To prevent corrupt texture runtime measurements from corrupting
the texture upload logic, we clamp the runtimes to the range
of [1,15000] microseconds.

If the corrupt runtimes are 0, this patch will effectively cause
us to always upload all pending textures.

This is a workaround until the async texture upload feature lands.

BUG=162699
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=171108

[reveman, 2012-12-04 21:24:09]

maybe make the upper limit a bit higher, otherwise lgtm.

https://codereview.chromium.org/11434111/diff/1/cc/texture_uploader.cc
File cc/texture_uploader.cc (right):

https://codereview.chromium.org/11434111/diff/1/cc/texture_uploader.cc#newcod...
cc/texture_uploader.cc:358: usElapsed = std::min(5000u, usElapsed);
you might want to make the limit a bit higher. like 15000u. 3 textures per frame
is not far from the real upload performance on some android devices. also there
shouldn't be any problem with making this too high as the
ResourceUpdateController will make sure do perform at least one update per
frame.

[commit-bot: I haz the power, 2012-12-04 21:34:45]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a lowly provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[nduca, 2012-12-04 21:37:03]

lgtm

[commit-bot: I haz the power, 2012-12-04 21:44:14]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/brianderson@chromium.org/11434111/3002

[commit-bot: I haz the power, 2012-12-04 21:45:44]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/brianderson@chromium.org/11434111/3002

[commit-bot: I haz the power, 2012-12-05 01:08:40]

Change committed as 171108