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

Issue 783689 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

24.5% regression in loading.desktop at 514458:514506

Project Member Reported by alexclarke@chromium.org, Nov 10 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 10 2017 

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

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


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

chromium-rel-win7-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 10 2017 


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/warm/Vietnamnet

Revision             Result                  N
chromium@514457      117.044 +- 109.684      21      good
chromium@514506      115.537 +- 92.6971      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=Vietnamnet loading.desktop

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 10 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: win_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/warm/Vietnamnet

Revision             Result                  N
chromium@514000      107.355 +- 82.6711      21      good
chromium@514396      115.661 +- 80.2913      21      unknown
chromium@514791      123.748 +- 70.7587      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=Vietnamnet loading.desktop

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

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


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

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 10 2017 


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/warm/Vietnamnet

Revision             Result                  N
chromium@514000      86.6324 +- 28.9503      21      good
chromium@514506      90.1058 +- 67.647       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=Vietnamnet loading.desktop

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

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


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

Comment 9 by 42576172...@developer.gserviceaccount.com, Nov 13 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: win_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/warm/Vietnamnet

Revision             Result                  N
chromium@514000      112.328 +- 84.8565      21      good
chromium@514500      119.039 +- 98.7805      21      unknown
chromium@515000      126.618 +- 88.0179      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=Vietnamnet loading.desktop

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

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


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

Comment 12 by 42576172...@developer.gserviceaccount.com, Jan 12 2018 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/13f3f2b7040000

Comment 13 by sullivan@chromium.org, Jan 12 2018 

Two of these test cases stopped running, and the regression went up over several revisions for all of them. Trying again with pinpoint to see if it can make sense of what happened.
Project Member

Comment 14 by 42576172...@developer.gserviceaccount.com, Jan 12 2018 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/16dab3ef040000

Comment 15 by sullivan@chromium.org, Jan 25 2018

Status: WontFix (was: Untriaged)
Looks like a WPR update in the catapult roll.
►

Sign in to add a comment