New issue
Advanced search Search tips

Issue 781952 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.6%-34.3% regression in thread_times.key_silk_cases at 512835:513039

Project Member Reported by mustaq@chromium.org, Nov 6 2017

Issue description

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

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


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

android-nexus5X
Cc: robertph...@google.com
Owner: robertph...@google.com
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author robertphillips@google.com ===

Hi robertphillips@google.com, 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 : Robert Phillips
  Commit : a92fe336f8d823fa96c5916508303f10ce30629e
  Date   : Tue Oct 31 20:36:30 2017
  Subject: Reenable Skia's deferred proxies

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_renderer_main_cpu_time_per_frame/http___jsfiddle.net_xLuvC_1_show_
  Change       : 37.10% | 2.40098977167 -> 3.29165722813

Revision             Result                    N
chromium@512834      2.40099 +- 0.119548       6      good
chromium@512937      2.42554 +- 0.107623       6      good
chromium@512941      2.31011 +- 0.250502       6      good
chromium@512943      2.39608 +- 0.169631       6      good
chromium@512944      3.1691 +- 0.25344         6      bad       <--
chromium@512950      3.22822 +- 0.0911578      6      bad
chromium@512963      3.17352 +- 0.211518       6      bad
chromium@512988      3.23363 +- 0.0944369      6      bad
chromium@513039      3.29166 +- 0.126845       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...jsfiddle.net.xLuvC.1.show. thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection

=== Auto-CCing suspected CL author robertphillips@google.com ===

Hi robertphillips@google.com, 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 : Robert Phillips
  Commit : a92fe336f8d823fa96c5916508303f10ce30629e
  Date   : Tue Oct 31 20:36:30 2017
  Subject: Reenable Skia's deferred proxies

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_renderer_main_cpu_time_per_frame/http___jsfiddle.net_xLuvC_1_show_
  Change       : 37.10% | 2.40098977167 -> 3.29165722813

Revision             Result                    N
chromium@512834      2.40099 +- 0.119548       6      good
chromium@512937      2.42554 +- 0.107623       6      good
chromium@512941      2.31011 +- 0.250502       6      good
chromium@512943      2.39608 +- 0.169631       6      good
chromium@512944      3.1691 +- 0.25344         6      bad       <--
chromium@512950      3.22822 +- 0.0911578      6      bad
chromium@512963      3.17352 +- 0.211518       6      bad
chromium@512988      3.23363 +- 0.0944369      6      bad
chromium@513039      3.29166 +- 0.126845       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...jsfiddle.net.xLuvC.1.show. thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Assigned)
This came back down.

Sign in to add a comment