GitLab

We plan to merge v8.browse and v8.runtimestats benchmarks into a single
benchmark. So, enable the memory metric on the v8.runtimestats benchmark.
Though the expectedQueueingTimeMetric is alredy enabled on v8.runtimestats*
it requires v8.compile trace events to work correctly. Also enable
v8.compile category for the expectedQueueingTimeMetric.

The only other metric tracked by v8.browsing and not by
v8.runtimestats.browsing is the v8 executionMetric. This is not required
since the runtimeStatsMetric is a super set of the executionMetric.


Bug: chromium:690921
Change-Id: I574c8c27515d3a62dc6d94c759be0eed32543f20
Reviewed-on: https://chromium-review.googlesource.com/574171Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Mythri Alle <mythria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487075}