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

Issue 758904 link

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



Sign in to add a comment

35.5% regression in loading.desktop at 496676:496774

Project Member Reported by kraynov@chromium.org, Aug 25 2017 
See the link to graphs below.
Project Member

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

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

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


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

win-high-dpi
Project Member

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


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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Vietnamnet

Revision             Result                  N
chromium@496675      192.251 +- 46.1293      21      good
chromium@496774      194.015 +- 87.3087      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=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/8970294990671864656


For feedback, file a bug with component Speed>Bisection

Comment 5 by sullivan@chromium.org, Sep 21 2017 

Trying a bisect on a wider revision range.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Sep 22 2017

Mergedinto: 758701
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Pavel Feldman
  Commit : 9ce7836fdec98fde42fc61347c4161077dbea0fc
  Date   : Wed Aug 23 07:07:21 2017
  Subject: DevTools: introduce lifecycle events reported over the page domain.

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Vietnamnet
  Change       : 63.50% | 127.371 -> 208.251833333

Revision             Result                  N
chromium@495726      127.371 +- 27.2042      6       good
chromium@496380      136.908 +- 45.6029      9       good
chromium@496544      122.76 +- 27.7869       6       good
chromium@496585      125.421 +- 22.3323      6       good
chromium@496606      136.456 +- 40.9317      9       good
chromium@496607      214.85 +- 180.163       9       bad       <--
chromium@496608      232.364 +- 90.4184      6       bad
chromium@496609      233.117 +- 120.355      6       bad
chromium@496611      200.722 +- 157.006      14      bad
chromium@496616      213.48 +- 159.833       9       bad
chromium@496626      202.632 +- 106.864      6       bad
chromium@496707      207.18 +- 118.746       6       bad
chromium@497033      208.252 +- 101.999      6       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=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/8967807548207869344


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

Sign in to add a comment