Large V8 traces causing OOM in memory benchmarks |
|||
Issue descriptionTracing overhead for v8 events can be more than 100MB. This is a problem for low-memory devices which crash with OOM on memory benchmarks. The three most frequent V8 events (V8.CompileCode, V8.CompileFullCode, and V8.ParseLazy) make up 2/3 of all events. By moving these events from the default 'v8' category into a separate category (e.g. 'v8.compile') we could reduce memory overhead of V8 tracing by 2/3 for benchmarks that don't care about v8 compilation time.
,
Jul 6 2016
sgtm Just make sure the existing telemetry tests don't break
,
Jul 6 2016
preparing benchmarks: https://codereview.chromium.org/2121263002/ adding new category: https://codereview.chromium.org/2121273002/
,
Jul 6 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/53450e52ffd2026c1af64b495ebd300069d8ec3e commit 53450e52ffd2026c1af64b495ebd300069d8ec3e Author: ulan <ulan@chromium.org> Date: Wed Jul 06 16:35:04 2016 Prepare for moving V8 compile events to disabled-by-default v8.compile category. This adds v8.compile category to benchmarks that track executionMetric. BUG= 625865 CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq Review-Url: https://codereview.chromium.org/2121263002 Cr-Commit-Position: refs/heads/master@{#403915} [modify] https://crrev.com/53450e52ffd2026c1af64b495ebd300069d8ec3e/tools/perf/benchmarks/v8.py
,
Jul 7 2016
,
Jul 18 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by u...@chromium.org
, Jul 5 2016