MemoryInfra: Tracing metrics benchmark should include memory-infra |
||||
Issue descriptionBackground context:go/memory-infra: memory profiling in chrome://tracing Memory-infra in background mode needs to be light and fast. This requires a benchmark to track the cpu overhead and trace size of memory infra events. these metrics can be added to existing tracing benchmark since the existing benchmark is meant for measuring tracing overhead for background tracing.
,
Jun 20 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d07de96446e595c4a810b592fedcb8bc026c9551 commit d07de96446e595c4a810b592fedcb8bc026c9551 Author: ssid <ssid@chromium.org> Date: Mon Jun 20 05:24:20 2016 [telemetry] Add new tracing benchmark for background mode memory-infra The memory infra category cannot be included in existing tracing benchmark because it creates large memory dumps in single event in "DETAILED" mode, so it changes the metrics measured. The memory-infra cannot be turned on just for "BACKGROUND" or "LIGHT" mode since the reference builds do not support the Tracing.Start api with trace config or the background mode at all. We also do not want to disable the tracing benchmark on reference builds. So, new benchamrk is added to measure overhead of memory-infra in background mode. The trcaingMetrics contains the metrics needs to track the overhead of memory infra in the traces, so the bencmark just tracks the tracingMetrics. BUG= 618514 CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq Review-Url: https://codereview.chromium.org/2052753002 Cr-Commit-Position: refs/heads/master@{#400628} [modify] https://crrev.com/d07de96446e595c4a810b592fedcb8bc026c9551/tools/perf/benchmarks/tracing.py
,
Jun 21 2016
,
Jun 22 2016
Metrics are now monitored.
,
Jan 4 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ssid@chromium.org
, Jun 14 2016