New issue
Advanced search Search tips

Issue 755300 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2%-54% regression in loading.desktop at 493117:493399

Project Member Reported by fmea...@chromium.org, Aug 14 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

chromium-rel-mac-retina
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
win-high-dpi
Project Member

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


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: daf7d437bb2fd277c9a7bbbfd6ea6e1e5545fe6b
  bad_revision : 955a7967ee52ade9fd54724a9f798a2fb7477ab3

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/FDA

Revision             Result                  N
chromium@493149      826.138 +- 5431.94      21      good
chromium@493215      643.106 +- 613.053      14      bad
chromium@493280      686.557 +- 907.661      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=FDA loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Sep 21 2017

๐Ÿ“ Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16b7e3ffb80000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 21 2017

๐Ÿ“ Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/100a0b2fb80000
Doh, bisect failed. Re-kicking on pinpoint.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Sep 21 2017

๐Ÿ“ Pinpoint job completed.
https://pinpoint-dot-chromeperf.appspot.com/job/16b7e3ffb80000
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Sep 21 2017

๐Ÿ“ Pinpoint job completed.
https://pinpoint-dot-chromeperf.appspot.com/job/100a0b2fb80000

Use swap time for all first paint times in TBM, UMA, UKM & web perf API
By shaseley@google.com ยท Thu Aug 10 00:40:36 2017
chromium@c3f876b18c07c50b360b93fb91ec67549b58deb8
Owner: panicker@chromium.org
panicker: assigning to you because this is similar to another issue: shaseley's CL "Use swap time for all first paint times in TBM, UMA, UKM & web perf API" regresses the loading.desktop benchmark (see #8). Should this be WontFix (metrics change)?
Status: WontFix (was: Untriaged)
Yes that is right. It is expected as we updated the metric to capture the cost of more of the rendering pipeline.

Sign in to add a comment