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

Issue 752112 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

18.3%-44.2% regression in loading.desktop at 490987:491262

Project Member Reported by alexclarke@chromium.org, Aug 3 2017

Issue description

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

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


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

chromium-rel-mac11-air

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/Chosun

Revision             Result                  N
chromium@490986      745.464 +- 169.093      21      good
chromium@491262      742.262 +- 129.207      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=Chosun loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/Chosun

Revision             Result                  N
chromium@490000      745.436 +- 149.28       21      good
chromium@491300      729.534 +- 117.703      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=Chosun loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection
Cc: charliea@chromium.org kouhei@chromium.org
Status: WontFix (was: Untriaged)
WontFix-ing because two bisects failed to repro and it's just a single page on a single device with no ref build. but +test owners and charliea: should a shift like this in cpu time happen and not be bisectable?

Sign in to add a comment