Disable tracing for profiling service.
Chrome suffers a significant performance degradation when both tracing and out-of-process heap-profiling are enabled. This is because the profiling service emits multiple trace events each time it reads from a profiling pipe, which happens around every 30 allocations or so. For more details, see the thread https://groups.google.com/a/google.com/forum/#!topic/chrome-benchmarking/rjNyxf_53lU. Bug: 769583 Change-Id: Iba006679154037268bb91b5baf09857a73aae8d2 Reviewed-on: https://chromium-review.googlesource.com/723747 Commit-Queue: Erik Chen <erikchen@chromium.org> Reviewed-by:Brett Wilson <brettw@chromium.org> Cr-Commit-Position: refs/heads/master@{#510265}
Showing
Please register or sign in to comment