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

Issue 776740 link

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



Sign in to add a comment

16.1%-28.1% regression in loading.desktop at 508345:508397

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 20 2017 

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

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


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

chromium-rel-mac11
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 20 2017 


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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/cold/ru.wikipedia

Revision             Result                  N
chromium@508344      412.332 +- 133.478      21      good
chromium@508397      408.852 +- 119.51       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=ru.wikipedia loading.desktop

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

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


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

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

Mergedinto: 775378
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Greg Kerr
  Commit : fcd7b94faa40dfc3e4e4be26f4e854dd14ef650c
  Date   : Thu Oct 12 22:48:50 2017
  Subject: Enable Finch Trial Test for MacV2Sandbox.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/cold/ru.wikipedia
  Change       : 13.97% | 412.404714286 -> 470.007777778

Revision             Result                  N
chromium@508344      412.405 +- 128.561      14      good
chromium@508443      406.865 +- 113.069      9       good
chromium@508492      402.177 +- 71.6898      9       good
chromium@508505      402.861 +- 62.379       9       good
chromium@508511      401.786 +- 76.5102      9       good
chromium@508512      407.25 +- 73.5775       9       good
chromium@508513      459.35 +- 67.5648       9       bad       <--
chromium@508514      459.143 +- 58.0897      9       bad
chromium@508517      461.737 +- 72.2899      9       bad
chromium@508541      470.008 +- 103.813      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=ru.wikipedia loading.desktop

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

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


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

Sign in to add a comment