New issue
Advanced search Search tips

Issue 776947 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Performance regression in blink_perf.image_decoder / decode-lossless-webp

Project Member Reported by bokan@chromium.org, Oct 20 2017

Issue description

Performance regression unrelated to  issue 775950  around r508735 - r508849

Looking at the following graphs:

ChromiumPerf/chromium-rel-mac12/memory.desktop / memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg /
ChromiumPerf/android-nexus5X/blink_perf.image_decoder / decode-lossless-webp
ChromiumPerf/android-webview-nexus5X/blink_perf.image_decoder / decode-lossless-webp
ChromiumPerf/chromium-rel-mac11-air/smoothness.tough_canvas_cases / frame_times /
ChromiumPerf/chromium-rel-mac11/blink_perf.canvas / transferFromImageBitmap
ChromiumPerf/chromium-rel-mac11-air/blink_perf.canvas / transferFromImageBitmap
ChromiumPerf/chromium-rel-mac12/blink_perf.canvas / transferFromImageBitmap
 
 
Project Member

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


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : blink_perf.image_decoder
  Metric       : decode-lossless-webp/decode-lossless-webp


Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.image_decoder

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

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


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

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 20 2017


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : blink_perf.canvas
  Metric       : transferFromImageBitmap/transferFromImageBitmap


Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.canvas

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

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


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

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

Mergedinto: 776395
Status: Duplicate (was: Started)

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

Suspected Commit
  Author : Robert Phillips
  Commit : 7f9b215695aae262797758b2e2a7b1d35fbe584f
  Date   : Thu Oct 12 13:42:01 2017
  Subject: Force all Intel GPUs to use draws instead of clears on Macs

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : memory.desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/TrivialCanvasPageSharedPageState
  Change       : 4.38% | 22157282.6667 -> 23127661.3333

Revision                             Result                  N
chromium@508740                      22157283 +- 954134      6      good
chromium@508800                      22084627 +- 437452      6      good
chromium@508830                      22053267 +- 719826      6      good
chromium@508838                      22252378 +- 982266      9      good
chromium@508839                      22194968 +- 236626      6      good
chromium@508839,skia@7f9b215695      23112072 +- 647037      6      bad       <--
chromium@508839,skia@5698c8a8a0      23253824 +- 492444      6      bad
chromium@508839,skia@cd975d5aa5      23086219 +- 357452      6      bad
chromium@508839,skia@1ba5b6baa8      23058315 +- 455533      6      bad
chromium@508839,skia@18e5cbbe65      23082120 +- 424353      6      bad
chromium@508839,skia@8efb9c5e82      23092381 +- 460962      6      bad
chromium@508840                      23138997 +- 532592      6      bad
chromium@508842                      23031020 +- 764515      9      bad
chromium@508845                      23222779 +- 586427      6      bad
chromium@508859                      23127661 +- 356887      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=TrivialCanvasPageSharedPageState memory.desktop

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

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


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

Comment 8 by 42576172...@developer.gserviceaccount.com, Oct 23 2017

Mergedinto: -776395 775433

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

Suspected Commit
  Author : Hans Wennborg
  Commit : 8316001e3f423f6ca2e7a9a7258c22944d16ae13
  Date   : Fri Oct 13 20:32:51 2017
  Subject: Roll Clang 313786:315613

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : blink_perf.image_decoder
  Metric       : decode-lossless-webp/decode-lossless-webp
  Change       : 6.23% | 375.570875 -> 398.959083333

Revision             Result                  N
chromium@508734      375.571 +- 3.59893      6      good
chromium@508792      375.615 +- 6.31291      6      good
chromium@508800      375.877 +- 3.06348      6      good
chromium@508802      376.155 +- 3.07149      6      good
chromium@508803      377.3 +- 8.21715        6      good
chromium@508804      395.36 +- 3.989         6      bad       <--
chromium@508807      395.984 +- 5.32901      6      bad
chromium@508821      392.686 +- 4.28741      6      bad
chromium@508849      398.959 +- 3.70495      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.image_decoder

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment