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

Issue 778605 link

Starred by 2 users
Status: Duplicate
Merged: issue 778587
Owner:
bokan@chromium.org
Closed: Jan 2018
Cc:
bokan@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

44.9% regression in thread_times.tough_scrolling_cases at 511404:511414

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

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

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

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


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

android-webview-nexus6
Project Member

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


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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/text_hover_10000_pixels_per_second

Revision             Result                  N
chromium@511403      310.7 +- 83.8209        21      good
chromium@511414      315.697 +- 137.028      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=text.hover.10000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

Comment 8 by sullivan@chromium.org, Jan 5 2018 

There are a LOT of regressions here. Kicking off a few more bisects on the most severe ones.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 5 2018

Cc: bokan@chromium.org
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)

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

Hi bokan@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 : David Bokan
  Commit : dbab215523c8d77a7b54fcf3776357b079c36899
  Date   : Tue Oct 24 14:24:10 2017
  Subject: Fix telemetry gesture speeds

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/text_constant_full_page_raster_10000_pixels_per_second

Revision                                 Result                   N
chromium@511393                          27.0329 +- 0.53947       6      good
chromium@511396                          26.6803 +- 1.63936       6      good
chromium@511397                          26.7316 +- 1.68696       6      good
chromium@511397,catapult@f9691b256a      27.486 +- 1.95309        6      good
chromium@511397,catapult@dbab215523      30.3995 +- 0.502865      6      bad       <--
chromium@511397,catapult@2f4cf37a9f      30.4509 +- 0.121402      6      bad
chromium@511398                          30.4132 +- 0.879323      6      bad
chromium@511402                          30.3008 +- 0.590786      6      bad
chromium@511410                          30.1293 +- 1.00819       6      bad
chromium@511426                          30.1517 +- 1.17909       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=text.constant.full.page.raster.10000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

Comment 10 by bokan@chromium.org, Jan 5 2018

Mergedinto: 778587
Status: Duplicate (was: Assigned)

Comment 11 by bokan@chromium.org, Jan 5 2018 

These look related to my fixing various issues in telemetry gestures and aren't real regressions.
Project Member

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

Status: Assigned (was: Duplicate)

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

Hi bokan@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 : David Bokan
  Commit : dbab215523c8d77a7b54fcf3776357b079c36899
  Date   : Tue Oct 24 14:24:10 2017
  Subject: Fix telemetry gesture speeds

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_constant_full_page_raster_30000_pixels_per_second

Revision                                 Result                     N
chromium@511382                          0.410273 +- 0.122088       6      good
chromium@511396                          0.428803 +- 0.0940159      6      good
chromium@511397                          0.484154 +- 0.206849       6      good
chromium@511397,catapult@f9691b256a      0.408651 +- 0.0751438      6      good
chromium@511397,catapult@dbab215523      2.00812 +- 0.0894525       6      bad       <--
chromium@511397,catapult@2f4cf37a9f      1.98263 +- 0.124923        6      bad
chromium@511398                          1.98931 +- 0.10308         6      bad
chromium@511400                          1.95757 +- 0.122973        6      bad
chromium@511403                          1.99723 +- 0.195537        6      bad
chromium@511410                          2.01381 +- 0.0884596       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=text.constant.full.page.raster.30000.pixels.per.second thread_times.tough_scrolling_cases

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

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


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

Comment 13 by 42576172...@developer.gserviceaccount.com, Jan 5 2018 


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

Suspected Commit
  Author : David Bokan
  Commit : dbab215523c8d77a7b54fcf3776357b079c36899
  Date   : Tue Oct 24 14:24:10 2017
  Subject: Fix telemetry gesture speeds

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_constant_full_page_raster_15000_pixels_per_second

Revision                                 Result                   N
chromium@511377                          1.19082 +- 0.685824      6      good
chromium@511388                          1.54009 +- 0.784529      6      good
chromium@511394                          1.29796 +- 0.304487      6      good
chromium@511397                          1.42361 +- 0.646497      6      good
chromium@511397,catapult@f9691b256a      1.40279 +- 0.348107      6      good
chromium@511397,catapult@dbab215523      6.00583 +- 0.288232      6      bad       <--
chromium@511397,catapult@2f4cf37a9f      5.94244 +- 0.288331      6      bad
chromium@511398                          6.06762 +- 0.398764      6      bad
chromium@511399                          6.02209 +- 0.184056      6      bad
chromium@511420                          6.00041 +- 0.237435      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=text.constant.full.page.raster.15000.pixels.per.second thread_times.tough_scrolling_cases

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

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


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

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


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

Suspected Commit
  Author : David Bokan
  Commit : dbab215523c8d77a7b54fcf3776357b079c36899
  Date   : Tue Oct 24 14:24:10 2017
  Subject: Fix telemetry gesture speeds

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_constant_full_page_raster_20000_pixels_per_second

Revision                                 Result                     N
chromium@511377                          0.439756 +- 0.56775        7      good
chromium@511388                          0.379471 +- 0.0196959      5      good
chromium@511394                          0.336165 +- 0.153062       7      good
chromium@511397                          0.364333 +- 0.172862       7      good
chromium@511397,catapult@f9691b256a      0.341433 +- 0.139546       7      good
chromium@511397,catapult@dbab215523      0.208322 +- 0.0370849      5      bad       <--
chromium@511397,catapult@2f4cf37a9f      0.217645 +- 0.173157       8      bad
chromium@511398                          0.221584 +- 0.145629       7      bad
chromium@511399                          0.206389 +- 0.063793       7      bad
chromium@511420                          0.201615 +- 0.0413145      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=text.constant.full.page.raster.20000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

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

Status: Duplicate (was: Assigned)
Thanks! Fixing duplicate status.
►

Sign in to add a comment