New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 706923 link

Starred by 2 users
Status: Fixed
Merged: issue 706866
Owner:
wangxianzhu@chromium.org
Closed: Jun 2017
Cc:
pdr@chromium.org
chrishtr@chromium.org
█ wkorman@chromium.org
vmp...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task

Blocked on:
issue 699198


Sign in to add a comment

SPInvalidation performance effects

Project Member Reported by wangxianzhu@chromium.org, Mar 30 2017 
This bug is to collect performance bisect results for performance changes around r460521 which enabled spinvalidation by default.

All alerts are here: https://chromeperf.appspot.com/group_report?rev=460521

Comment 4 by schenney@chromium.org, Mar 30 2017

Labels: -Type-Bug BugSource-Team PaintTeamTriaged-20170330 Type-Task
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Mar 30 2017 


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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_raster_cpu_time_per_frame/https___www.flickr.com_

Revision             Result                    N
chromium@460464      3.62684 +- 0.0933837      21      good
chromium@460532      3.64085 +- 0.247555       21      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=https...www.flickr.com. thread_times.simple_mobile_sites

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983672793032984608

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5465344233177088


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Mar 30 2017 


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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_raster_cpu_time_per_frame/https___www.flickr.com_

Revision             Result                   N
chromium@460464      3.63105 +- 0.120811      21      good
chromium@460532      3.65545 +- 0.528912      21      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=https...www.flickr.com. thread_times.simple_mobile_sites

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983672756120970704

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6133665672724480


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Mar 30 2017 


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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame

Revision             Result                   N
chromium@460464      3.14141 +- 0.542943      21      good
chromium@460532      3.1288 +- 0.590276       21      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 thread_times.simple_mobile_sites

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983668588834339744

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5021157641682944


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Comment 10 by chrishtr@chromium.org, Mar 30 2017

Blockedon: 699198
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Mar 31 2017

Mergedinto: 706866
Status: Duplicate (was: Assigned)

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

Suspected Commit
  Author : ericrk
  Commit : 2f952e4c39887d65126ca4cd67a897fc6d409fb9
  Date   : Wed Mar 29 22:15:32 2017
  Subject: Enable CrOS/Android DefaultEnableGpuRasterization field trial for bots

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_raster_cpu_time_per_frame/https___www.flickr.com_
  Change       : 89.04% | 3.51372135524 -> 0.385201552571

Revision             Result                     N
chromium@460532      3.51372 +- 0.177036        6      good
chromium@460542      3.47482 +- 0.0765304       6      good
chromium@460547      3.48152 +- 0.0929753       6      good
chromium@460548      3.5449 +- 0.171366         6      good
chromium@460549      0.389965 +- 0.0436638      6      bad       <--
chromium@460550      0.381884 +- 0.0172552      6      bad
chromium@460552      0.374826 +- 0.0211545      6      bad
chromium@460572      0.385202 +- 0.025873       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=https...www.flickr.com. thread_times.simple_mobile_sites

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983660914168803216

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5582631736967168


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Comment 12 by wangxianzhu@chromium.org, Mar 31 2017

Status: Assigned (was: Duplicate)
The improvement of thread_raster_cpu_time_per_frame is unrelated. The drop in range r460464:r460532 is a false one, and the real drop is in the next range.
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Mar 31 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    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science


Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.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 memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983672697927483792

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6340355336699904


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Comment 16 by wangxianzhu@chromium.org, Jun 25 2017

Status: Fixed (was: Assigned)
►

Sign in to add a comment