New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 791993 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 792061
Owner: ----
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10%-34.8% regression in blink_perf.parser at 519911:520079

Project Member Reported by pmeenan@chromium.org, Dec 5 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=791993

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=377c102b843842a327fb699d8f6773222f4803faaaf34a7ceb6a7f7562720e43


Bot(s) for this bug's original alert(s):

android-nexus5
android-nexus7v2
chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-mac12-mini-8gb
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual
win-high-dpi

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : query-selector-all-last/query-selector-all-last
  Change       : 9.82% | 68.380909305 -> 61.6651480319

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4f59a790e19f97e8bbdbb6e7960883c1e1cf0234..c47b4d110a697afa6a6ee4d4748028312c65ec19


Revision             Result                  N
chromium@519996      68.3809 +- 1.26958      6        good
chromium@520034      68.6093 +- 1.61607      6        good
chromium@520053      68.0503 +- 2.29566      6        good
chromium@520058      67.9967 +- 1.75718      6        good
chromium@520060      68.4126 +- 1.34373      6        good
chromium@520061      ---                     ---      build failure
chromium@520062      61.465 +- 0.795498      6        bad
chromium@520063      61.7439 +- 1.56534      6        bad
chromium@520072      61.6651 +- 1.80869      6        bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8961040662825100528


For feedback, file a bug with component Speed>Bisection
Mergedinto: 792061
Status: Duplicate (was: Untriaged)

Sign in to add a comment