New issue
Advanced search Search tips

Issue 792940 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

14.4% regression in thread_times.simple_mobile_sites at 521610:521673

Project Member Reported by npm@chromium.org, Dec 7 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=792940

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


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

android-webview-nexus5X

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_GPU_cpu_time_per_frame/http___m.nytimes.com_

Revision             Result                     N
chromium@521609      0.671832 +- 0.0529057      21      good
chromium@521673      0.667482 +- 0.0680728      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=http...m.nytimes.com. thread_times.simple_mobile_sites

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Dec 11 2017

Mergedinto: 792452
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Chris Harrelson
  Commit : a3e4477c29d087d3708dbcb4dc5a90985c2b45e3
  Date   : Tue Dec 05 01:51:58 2017
  Subject: [PE] Turn on half-width tiles for all platforms and devices.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_total_fast_path_cpu_time_per_frame/http___www.nyc.gov
  Change       : 3.12% | 12.1028962729 -> 12.4799345101

Revision             Result                   N
chromium@521486      12.1029 +- 0.165972      6      good
chromium@521549      12.0817 +- 0.260789      6      good
chromium@521580      12.0526 +- 0.255233      6      good
chromium@521584      12.1058 +- 0.231693      6      good
chromium@521585      12.1525 +- 0.263366      6      good
chromium@521586      12.5138 +- 0.316775      6      bad       <--
chromium@521588      12.5394 +- 0.147055      6      bad
chromium@521596      12.4975 +- 0.236636      6      bad
chromium@521611      12.4799 +- 0.208516      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...www.nyc.gov thread_times.simple_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment