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

Issue 779811 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

6.2%-621.8% regression in smoothness.gpu_rasterization.top_25_smooth at 511313:511540

Project Member Reported by briander...@chromium.org, Oct 30 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-one
Project Member

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


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_constant_full_page_raster_60000_pixels_per_second
  Change       : 4.93% | 4.2660650348 -> 4.06681517706

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/cd32fdf5709b0ec9aa71502dfec1e84f8f3567c3..a198fc24fe25a6f04bbe2264b28571f580bfe579


Revision             Result                   N
chromium@511424      4.26607 +- 0.434166      14       good
chromium@511428      4.21751 +- 0.404596      14       good
chromium@511429      ---                      ---      build failure
chromium@511430      ---                      ---      build failure
chromium@511431      4.12691 +- 0.439805      14       bad
chromium@511432      4.11186 +- 0.344352      14       bad
chromium@511439      4.13811 +- 0.299343      14       bad
chromium@511453      4.13895 +- 0.397708      14       bad
chromium@511482      4.07246 +- 0.254046      9        bad
chromium@511540      4.06682 +- 0.228927      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.constant.full.page.raster.60000.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/8964269742107752480


For feedback, file a bug with component Speed>Bisection
Owner: yukishiino@chromium.org
Status: Assigned (was: Untriaged)
@yukishiino: Of the 3 patches in the range https://chromium.googlesource.com/chromium/src/+/a198fc24fe25a6f04bbe2264b28571f580bfe579 looks the most suspect.

Can you take a look?
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 31 2017

Mergedinto: 778587
Status: Duplicate (was: Assigned)

=== 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_15000_pixels_per_second
  Change       : 9.31% | 25.947428276 -> 28.3643747072

Revision                                 Result                   N
chromium@511393                          25.9474 +- 0.287926      6      good
chromium@511396                          25.8272 +- 0.903972      6      good
chromium@511397                          26.2463 +- 1.20066       6      good
chromium@511397,catapult@f9691b256a      26.7621 +- 1.88498       6      good
chromium@511397,catapult@dbab215523      28.5284 +- 0.545044      6      bad       <--
chromium@511397,catapult@2f4cf37a9f      28.2683 +- 0.770058      6      bad
chromium@511398                          28.149 +- 0.311488       6      bad
chromium@511402                          28.1501 +- 1.15455       6      bad
chromium@511410                          28.4712 +- 0.642025      6      bad
chromium@511426                          28.3644 +- 0.304836      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/8964188835348897008


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment