Revert of Enabled gpu_times metrics. (patchset #1 id:1 of https://codereview.chromium...
commite917b49708a65bcf4295ee872ea2fb8e94b3bbcf
authornednguyen <nednguyen@google.com>
Wed, 25 Feb 2015 13:23:42 +0000 (25 05:23 -0800)
committerCommit bot <commit-bot@chromium.org>
Wed, 25 Feb 2015 13:24:15 +0000 (25 13:24 +0000)
treee474ca70d3cdf3b3411f3482808bd7595a232710
parent949a0eb48a3e7aec1d8e347ab03902055ede9a5b
Revert of Enabled gpu_times metrics. (patchset #1 id:1 of https://codereview.chromium.org/937073003/)

Reason for revert:
Causing not redness.

Original issue's description:
> Enabled gpu_times metrics.
>
> The issue where gpu_times would use too much memory has been fixed:
> https://codereview.chromium.org/920523002
>
> In order to prepare for future changes where additional metrics
> will be added to the TBM module, I have also preemptively added a
> filter function which filters out values relating to gpu_times.
>
> R=nednguyen@chromium.org
> BUG=455292, 453131
> TEST=local runs measuring memory usage shows ~700mb
>
> Committed: https://crrev.com/ed5b27a7459e35248992fd5549b72b5731a8baa4
> Cr-Commit-Position: refs/heads/master@{#317974}

TBR=dyen@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=455292, 453131

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

Cr-Commit-Position: refs/heads/master@{#318034}
tools/perf/benchmarks/gpu_times.py
tools/telemetry/telemetry/web_perf/metrics/gpu_timeline.py