New issue
Advanced search Search tips

Issue 771190 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9.8%-52.4% regression in thread_times.{key_idle_power_cases,tough_compositor_cases,key_silk_cases} at 505545:505641

Project Member Reported by majidvp@chromium.org, Oct 3 2017

Issue description

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

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


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

android-nexus7v2
android-webview-nexus6
Cc: u...@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Untriaged)

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

Hi ulan@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 : Ulan Degenbaev
  Commit : 7c1b01154a460dec5da40a9c8d5ae4e44eea8e4e
  Date   : Fri Sep 29 11:38:50 2017
  Subject: [heap] Enable concurrent marking on all platforms.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_other_cpu_time_per_frame/http___wiltzius.github.io_shape-shifter_
  Change       : 48.34% | 0.38638100149 -> 0.573169103949

Revision                           Result                     N
chromium@505546                    0.386381 +- 0.0231377      6      good
chromium@505556                    0.388128 +- 0.0191461      6      good
chromium@505558                    0.398562 +- 0.0369759      6      good
chromium@505558,v8@5005a62fe0      0.389048 +- 0.0253895      6      good
chromium@505558,v8@7c1b01154a      0.613904 +- 0.0343567      6      bad       <--
chromium@505559                    0.585423 +- 0.0614658      6      bad
chromium@505561                    0.561316 +- 0.0446402      6      bad
chromium@505565                    0.573169 +- 0.058603       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...wiltzius.github.io.shape.shifter. 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/8966742995993760576


For feedback, file a bug with component Speed>Bisection
Cc: mvstan...@chromium.org
 Issue 771551  has been merged into this issue.
 Issue 771549  has been merged into this issue.
 Issue 771576  has been merged into this issue.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Oct 24 2017

Cc: jgruber@chromium.org
 Issue 775865  has been merged into this issue.

Comment 8 by u...@chromium.org, Oct 24 2017

Status: WontFix (was: Assigned)
The regressions here are expected. We move work to background cpus and do faster progress in garbage collection.
Labels: Performance-Tradeoff

Sign in to add a comment