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

Issue 760144 link

Starred by 1 user
Status: Duplicate
Merged: issue 759671
Owner: ----
Closed: Oct 2017
Cc:
█ pmeenan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

31.3%-101.8% regression in loading.desktop at 494831:495001

Project Member Reported by pmeenan@chromium.org, Aug 29 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 29 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=760144

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


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

chromium-rel-mac11
chromium-rel-mac12
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 29 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/HTML5Rocks


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=HTML5Rocks loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 5 by sullivan@chromium.org, Oct 9 2017 

Re-bisecting on other device/wider range.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 10 2017

Mergedinto: 759671
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Greg Kerr
  Commit : 9705b7aaabf4c81d4e9cb13174338df9bde61cc4
  Date   : Tue Aug 15 19:42:42 2017
  Subject: Enable Finch Trial Test for MacV2Sandbox.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/Orange
  Change       : 47.32% | 79.2028333333 -> 116.67975

Revision             Result                  N
chromium@494345      79.2028 +- 11.008       6      good
chromium@494444      82.2294 +- 7.33325      6      good
chromium@494493      83.9703 +- 17.9343      6      good
chromium@494499      87.7066 +- 9.16722      6      good
chromium@494501      81.316 +- 10.0654       6      good
chromium@494502      116.39 +- 7.12275       6      bad       <--
chromium@494505      114.933 +- 12.4582      6      bad
chromium@494517      116.872 +- 8.98344      6      bad
chromium@494542      116.285 +- 17.1495      6      bad
chromium@494738      116.759 +- 13.5083      6      bad
chromium@495131      116.68 +- 13.3678       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Orange loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment