New issue
Advanced search Search tips

Issue 721294 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

34% regression in page_cycler_v2_site_isolation.basic_oopif at 470372:470433

Project Member Reported by hjd@google.com, May 11 2017

Issue description

See the link to graphs below.
 

Comment 1 by hjd@google.com, May 11 2017

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyrukqwkM


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

chromium-rel-mac11-pro
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 11 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : page_cycler_v2_site_isolation.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.fifa.com_

Revision             Result                  N
chromium@470371      230.454 +- 178.453      21      good
chromium@470433      213.812 +- 176.429      21      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=http...www.fifa.com. page_cycler_v2_site_isolation.basic_oopif

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979900103453759920

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5808644320395264


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Comment 6 by hjd@chromium.org, May 11 2017

Started wider bisect.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, May 11 2017


=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : page_cycler_v2_site_isolation.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.fifa.com_

Revision             Result                  N
chromium@470293      191.397 +- 26.6055      14      good
chromium@470328      192.657 +- 63.334       21      good
chromium@470345      223.324 +- 205.114      21      unknown
chromium@470361      235.679 +- 166.706      21      bad
chromium@470432      245.317 +- 113.395      14      bad
chromium@470570      251.575 +- 76.4081      9       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=http...www.fifa.com. page_cycler_v2_site_isolation.basic_oopif

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979890504605502736

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6670478900461568


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Comment 8 by hjd@chromium.org, May 11 2017

With luck crbug/721293 which catch CL otherwise I can retry bisect.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, May 11 2017


=== 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: mac_pro_perf_bisect
  Benchmark    : page_cycler_v2_site_isolation.basic_oopif
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.fifa.com_
  Change       : 13.85% | 254.489 -> 219.230142857

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/84d8af49b69b6ab89bde2d657b96c5f280fd439c..4093b79b5e57860bd7b90a9bc41bae5629d84c61


Revision             Result                  N
chromium@470371      254.489 +- 131.846      14       good
chromium@470372      ---                     ---      build failure
chromium@470373      ---                     ---      build failure
chromium@470374      227.306 +- 164.618      14       bad
chromium@470377      212.625 +- 150.246      14       bad
chromium@470383      215.718 +- 137.602      14       bad
chromium@470401      208.557 +- 125.808      14       bad
chromium@470433      219.23 +- 134.223       14       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=http...www.fifa.com. page_cycler_v2_site_isolation.basic_oopif

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979892117319395280

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5808644320395264


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Comment 10 by hjd@chromium.org, May 12 2017

Mergedinto: 721293
Status: Duplicate (was: Untriaged)

Sign in to add a comment