Enabled gpu_times metrics.

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}

[David Yen, 2015-02-24 23:16:34]

dyen@chromium.org changed reviewers:
+ nednguyen@google.com
- nednguyen@chromium.org

[David Yen, 2015-02-24 23:16:48]

On 2015/02/24 23:16:15, David Yen wrote:

+nednguyen

[nednguyen, 2015-02-25 02:55:25]

https://codereview.chromium.org/937073003/diff/1/tools/telemetry/telemetry/we...
File tools/telemetry/telemetry/web_perf/metrics/gpu_timeline.py (right):

https://codereview.chromium.org/937073003/diff/1/tools/telemetry/telemetry/we...
tools/telemetry/telemetry/web_perf/metrics/gpu_timeline.py:32:
super(GPUTimelineValue, self).__init__(page, name, 'ms', value)
+1 
I like this.

[nednguyen, 2015-02-25 02:55:27]

lgtm

[David Yen, 2015-02-25 03:07:48]

The CQ bit was checked by dyen@chromium.org

[commit-bot: I haz the power, 2015-02-25 03:09:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/937073003/1

[commit-bot: I haz the power, 2015-02-25 04:58:10]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-25 04:58:59]

Patchset 1 (id:??) landed as
https://crrev.com/ed5b27a7459e35248992fd5549b72b5731a8baa4
Cr-Commit-Position: refs/heads/master@{#317974}

[nednguyen, 2015-02-25 13:22:55]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/952133003/ by nednguyen@google.com.

The reason for reverting is: Causing not redness..