New issue
Advanced search Search tips

Issue 753623 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
perezju@chromium.org
sullivan@chromium.org
nedngu...@google.com
primiano@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

system_health benchmarks take 3x longer to run than they should.

Project Member Reported by erikc...@chromium.org, Aug 9 2017 
In https://bugs.chromium.org/p/chromium/issues/detail?id=753591, I fix a simple bug to reduce the runtime from 4m30s to 1m30s.

The remaining 90 seconds of the runtime are roughly equally divided between:
1) Actually running the test. 
2) sending a 15MB trace file from devtools to telemetry
3) Doing some post-processing on the trace file

Both (2) and (3) are suspiciously high. I spent about 1hr digging into this, but didn't make any progress, so I'm moving on. cc-ing some other individuals who might be interested.

Comment 1 by erikc...@chromium.org, Aug 9 2017 

And for reference, I was running the following code:

"""
./tools/perf/run_benchmark --browser=exact --browser-executable=./out/gn/Chromium.app/Contents/MacOS/Chromium system_health.common_desktop --story-filter='load:search:amazon' --pageset-repeat=1 --output-format=json --output-format=html
"""

on a macOS 10.12 Desktop.

Comment 2 by erikc...@chromium.org, Aug 9 2017

Status: WontFix (was: Untriaged)
aargh, I was accidentally using a build of Chrome that had out-of-process heap profiling enabled, which caused trace bloat, hence the longer times. With it turned off, the whole process takes 40s.
►

Sign in to add a comment