New issue
Advanced search Search tips

Issue 774089 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

8.4%-63.9% regression in thread_times.key_silk_cases at 507598:507726

Project Member Reported by primiano@chromium.org, Oct 12 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 12 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_nexus6_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_raster_cpu_time_per_frame/http___jsfiddle.net_xLuvC_1_show_
  Change       : 61.62% | 12.6715078662 -> 20.4800591159

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/skia/+log/df071d78850d6cfcb6fb891316757e33574ee512..c7e66ea989006b6f21ccf4e4c33644a55b5455ec


Revision                             Result                   N
chromium@507597                      12.6715 +- 0.277505      6        good
chromium@507662                      12.772 +- 0.547905       6        good
chromium@507662,skia@df071d7885      12.8917 +- 0.216541      6        good
chromium@507662,skia@32a6924162      ---                      ---      build failure
chromium@507662,skia@c7e66ea989      20.8939 +- 0.772912      6        bad
chromium@507662,skia@37387c80cc      20.8013 +- 0.465784      6        bad
chromium@507662,skia@c4b015ad5f      20.9639 +- 0.464028      6        bad
chromium@507662,skia@df007e1a7a      20.7183 +- 0.72398       6        bad
chromium@507663                      20.7799 +- 0.45549       6        bad
chromium@507664                      20.8172 +- 0.270962      6        bad
chromium@507666                      20.6853 +- 0.287151      6        bad
chromium@507670                      20.7395 +- 0.215971      6        bad
chromium@507678                      20.864 +- 0.369643       6        bad
chromium@507694                      20.5721 +- 0.78761       6        bad
chromium@507726                      20.4801 +- 1.21078       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/8965932591099083744


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
Bisect unable to find culprit, this regression exists in stable. Ignoring.

Sign in to add a comment