New issue
Advanced search Search tips

Issue 785574 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 785572
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero regression in smoothness.tough_scrolling_cases at 515993:516094

Project Member Reported by m...@chromium.org, Nov 16 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-one
Project Member

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


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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.tough_scrolling_cases
  Metric       : mean_pixels_approximated/text_hover_40000_pixels_per_second

Revision             Result                  N
chromium@515992      0.66 +- 1.81902         21      good
chromium@516094      0.593905 +- 1.8641      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=text.hover.40000.pixels.per.second smoothness.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/8962812562732913344


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 16 2017

Mergedinto: 785572
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : David Bokan
  Commit : cbeb064ce8a422528be2e2e6eca1942333628f01
  Date   : Mon Nov 13 17:00:01 2017
  Subject: Fix telemetry gesture wheel scrolling on Android

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.tough_scrolling_cases
  Metric       : mean_pixels_approximated/text_hover_50000_pixels_per_second
  Change       : 738.58% | 0.0642222222222 -> 0.538555555556

Revision             Result                     N
chromium@515881      0.0642222 +- 0.544944      9      good
chromium@515935      0.0 +- 0.0                 6      good
chromium@515962      0.0 +- 0.0                 6      good
chromium@515966      0.0 +- 0.0                 6      good
chromium@515967      0.605833 +- 0.753203       6      bad       <--
chromium@515968      0.548667 +- 0.721891       6      bad
chromium@515969      0.528 +- 0.764856          6      bad
chromium@515975      0.410333 +- 0.734891       6      bad
chromium@515988      0.273667 +- 0.356299       6      bad
chromium@516094      0.538556 +- 1.48603        9      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.hover.50000.pixels.per.second smoothness.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/8962733255871699888


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment