New issue
Advanced search Search tips

Issue 749354 link

Starred by 1 user
Status: Duplicate
Merged: issue 747805
Owner: ----
Closed: Jul 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

31.7%-124.7% regression in loading.desktop at 488642:488806

Project Member Reported by m...@chromium.org, Jul 27 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 27 2017 

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

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


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

chromium-rel-mac11-pro
chromium-rel-win10
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 27 2017 


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/NatGeo

Revision             Result                  N
chromium@488707      807.512 +- 518.599      21      good
chromium@488806      852.818 +- 445.396      21      bad

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

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by m...@chromium.org, Jul 27 2017

Cc: -m...@chromium.org
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jul 28 2017

Mergedinto: 747805
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Daniel Vogelheim
  Commit : 5578c07d877cb8bf3ee41439ea1c8ff9c0dd7394
  Date   : Fri Jul 21 14:03:19 2017
  Subject: ScriptRunner can initiate script streaming.

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-cold/yahoo.co.jp
  Change       : 13.15% | 1841.82692857 -> 2074.46707143

Revision             Result                  N
chromium@488633      1841.83 +- 705.48       14      good
chromium@488646      1757.47 +- 579.334      14      good
chromium@488647      1810.15 +- 665.607      14      good
chromium@488648      2063.48 +- 74.4525      9       bad       <--
chromium@488649      2051.88 +- 77.8902      14      bad
chromium@488652      2059.07 +- 35.0172      9       bad
chromium@488658      2060.55 +- 113.958      14      bad
chromium@488682      2061.46 +- 35.9353      9       bad
chromium@488733      2074.47 +- 192.538      14      bad

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

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

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


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

Sign in to add a comment