New issue
Advanced search Search tips

Issue 679396 link

Starred by 1 user
Status: Duplicate
Merged: issue 679324
Owner:
dtapu...@chromium.org
Closed: Jan 2017
Cc:
dtapu...@chromium.org
schenney@chromium.org
benhenry@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.2%-192.6% regression in smoothness.key_mobile_sites_smooth at 441470:441632

Project Member Reported by benhenry@google.com, Jan 9 2017 
Links in next comment
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 9 2017 


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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___mobile-news.sandbox.google.com_news_pt0

Revision             Result                 N
chromium@441588      20.7872 +- 33.467      21      good
chromium@441599      20.466 +- 29.1821      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...mobile.news.sandbox.google.com.news.pt0 smoothness.sync_scroll.key_mobile_sites_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990923793627797520

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4926390840852480


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jan 9 2017

Cc: schenney@chromium.org
Owner: schenney@chromium.org

=== Auto-CCing suspected CL author schenney@chromium.org ===

Hi schenney@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : schenney
  Commit : d3ba7664a7ebc6e74861602eb9696c7ca0a4ed2e
  Date   : Thu Jan 05 06:01:46 2017
  Subject: Fix border radius on composited children.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___worldjournal.com_
  Change       : 77.60% | 43.3183333333 -> 76.933

Revision             Result                  N
chromium@441588      43.3183 +- 4.09034      6      good
chromium@441591      43.5723 +- 6.38245      6      good
chromium@441592      75.8008 +- 8.03407      6      bad       <--
chromium@441593      74.979 +- 12.3153       6      bad
chromium@441594      77.6167 +- 14.5323      6      bad
chromium@441599      79.4518 +- 10.0574      6      bad
chromium@441610      79.3992 +- 8.34967      6      bad
chromium@441632      76.933 +- 6.464         6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...worldjournal.com. smoothness.sync_scroll.key_mobile_sites_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990910346189298800

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5804494757036032


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 9 2017 


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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___mobile-news.sandbox.google.com_news_pt0

Revision             Result                  N
chromium@441539      22.1348 +- 25.2145      21      good
chromium@441602      24.6661 +- 7.1249       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...mobile.news.sandbox.google.com.news.pt0 smoothness.sync_scroll.key_mobile_sites_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990910343496365936

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5863686385696768


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Jan 9 2017

Mergedinto: 679324
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : dtapuska
  Commit : 5494d50ab65532c64a28e91e23b0a722ebbfe8ed
  Date   : Wed Jan 04 22:02:35 2017
  Subject: Remove the requirement to only rAF align non-blocking touch moves.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___mobile-news.sandbox.google.com_news_pt0
  Change       : 185.78% | 15.4523333333 -> 44.159

Revision             Result                   N
chromium@441469      15.4523 +- 1.60177       6      good
chromium@441474      15.8305 +- 1.50937       6      good
chromium@441476      15.0918 +- 0.709437      6      good
chromium@441477      15.4662 +- 0.920697      6      good
chromium@441478      40.6007 +- 16.3878       6      bad       <--
chromium@441487      42.771 +- 2.30084        6      bad
chromium@441505      43.5178 +- 0.228514      6      bad
chromium@441540      39.7242 +- 17.7695       6      bad
chromium@441611      44.159 +- 3.78103        6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...mobile.news.sandbox.google.com.news.pt0 smoothness.sync_scroll.key_mobile_sites_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990910334536950608

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5902949902974976


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Jan 9 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: android_nexus6_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.polymer
  Metric       : input_event_latency_discrepancy/input_event_latency_discrepancy

Revision             Result                  N
chromium@441524      211.488 +- 721.099      48      good
chromium@441577      215.689 +- 777.843      48      good
chromium@441601      263.912 +- 825.51       48      unknown
chromium@441624      275.417 +- 841.274      48      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.gpu_rasterization.polymer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8990910372097402480

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5884621666910208


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Mar 22 2017 


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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : mean_input_event_latency/http___mobile-news.sandbox.google.com_news_pt0

Revision             Result                 N
chromium@441588      20.7872 +- 33.467      21      good
chromium@441599      20.466 +- 29.1821      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...mobile.news.sandbox.google.com.news.pt0 smoothness.sync_scroll.key_mobile_sites_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8984378622697512240

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4926390840852480


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 15 by 42576172...@developer.gserviceaccount.com, Mar 24 2017

Cc: dtapu...@chromium.org
Owner: dtapu...@chromium.org

=== Auto-CCing suspected CL author dtapuska@chromium.org ===

Hi dtapuska@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : dtapuska
  Commit : 5494d50ab65532c64a28e91e23b0a722ebbfe8ed
  Date   : Wed Jan 04 22:02:35 2017
  Subject: Remove the requirement to only rAF align non-blocking touch moves.

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : first_gesture_scroll_update_latency/Docs  (1 open document tab)
  Change       : 209.78% | 9.69811111111 -> 22.2971666667

Revision             Result                  N
chromium@441458      9.69811 +- 24.7341      9      good
chromium@441469      20.0548 +- 115.943      9      good
chromium@441475      8.34422 +- 20.4886      9      good
chromium@441477      12.6701 +- 57.5711      9      good
chromium@441478      24.348 +- 19.9997       9      bad       <--
chromium@441480      25.433 +- 20.5277       9      bad
chromium@441501      30.356 +- 43.8274       6      bad
chromium@441543      22.2972 +- 2.7842       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=Docs...1.open.document.tab. smoothness.top_25_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8984287868783426432

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4926390840852480


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
►

Sign in to add a comment