New issue
Advanced search Search tips

Issue 738836 link

Starred by 1 user
Status: Assigned
Owner:
ishell@chromium.org
Cc:
jgruber@chromium.org
ishell@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6%-19.8% regression in system_health.memory_desktop at 482436:482966

Project Member Reported by jgruber@chromium.org, Jul 3 2017 
See the link to graphs below.

Comment 1 by jgruber@chromium.org, Jul 3 2017 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnubltgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7pvR-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnoSt4wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrpfX-gkM


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 3 2017 


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@482845      5.32319 +- 11.8824      21      good
chromium@482917      5.98914 +- 13.771       21      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=browse.social.twitter v8.runtimestats.browsing_desktop

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Jul 3 2017 


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@482845      7.89619 +- 13.2199      21      good
chromium@482917      6.78052 +- 15.8627      21      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=browse.social.twitter v8.runtimestats.browsing_desktop

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

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


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

Comment 9 by 42576172...@developer.gserviceaccount.com, Jul 4 2017 


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@482845      8.63048 +- 15.4525      21      good
chromium@482917      8.56367 +- 22.0988      21      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=browse.social.twitter v8.runtimestats.browsing_desktop

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

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


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

Comment 11 by 42576172...@developer.gserviceaccount.com, Jul 4 2017

Cc: ishell@chromium.org
Owner: ishell@chromium.org

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

Hi ishell@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 : Igor Sheludko
  Commit : 5dd179933c32b0ea992b53b6fc82db0b88a85734
  Date   : Tue Jun 27 15:26:10 2017
  Subject: Reland "[runtime] Make all built-in functions strict."

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_baidu
  Change       : 3.52% | 8273920.0 -> 8636888.61538

Revision                           Result                  N
chromium@482780                    8273920 +- 0.0          14      good
chromium@482829                    8273920 +- 0.0          14      good
chromium@482854                    8311369 +- 505217       14      good
chromium@482860                    8373784 +- 943441       21      good
chromium@482863                    8273920 +- 0.0          9       good
chromium@482864                    8332174 +- 494303       9       good
chromium@482864,v8@ab028038db      8390428 +- 653902       9       good
chromium@482864,v8@2ac6dae6fa      8390428 +- 653902       9       good
chromium@482864,v8@5dd179933c      8798208 +- 0.0          9       bad       <--
chromium@482864,v8@a00eb6833c      8798208 +- 0.0          9       bad
chromium@482865                    8798208 +- 0.0          9       bad
chromium@482866                    8623445 +- 1353706      21      bad
chromium@482878                    8636889 +- 872468       13      bad

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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.baidu system_health.memory_desktop

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

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


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

Comment 12 by 42576172...@developer.gserviceaccount.com, Jul 4 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: winx64nvidia_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_baidu
  Change       : 4.46% | 8311369.14286 -> 8648411.42857

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/2ac6dae6faecf97b1b124bf56e715085638541d6..0a91a4c90f28be3a769323f99c95e698b09b0c09


Revision                           Result                 N
chromium@482767                    8311369 +- 505217      14       good
chromium@482821                    8273920 +- 0.0         9        good
chromium@482848                    8348818 +- 686454      14       good
chromium@482861                    8273920 +- 0.0         6        good
chromium@482864                    8273920 +- 0.0         6        good
chromium@482864,v8@ab028038db      8348818 +- 686454      14       good
chromium@482864,v8@2ac6dae6fa      8348818 +- 840731      21       good
chromium@482864,v8@5dd179933c      ---                    ---      build failure
chromium@482864,v8@0a91a4c90f      8648411 +- 886208      14       bad
chromium@482864,v8@a00eb6833c      8760759 +- 505217      14       bad
chromium@482865                    8710827 +- 478607      6        bad
chromium@482866                    8710827 +- 478607      6        bad
chromium@482869                    8798208 +- 0.0         6        bad
chromium@482875                    8648411 +- 886208      14       bad

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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.baidu system_health.memory_desktop

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

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


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

Comment 13 by 42576172...@developer.gserviceaccount.com, Jul 5 2017 


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@482845      8.791 +- 17.5482        21      good
chromium@482917      7.92652 +- 18.4281      21      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=browse.social.twitter v8.runtimestats.browsing_desktop

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

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


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

Comment 15 by 42576172...@developer.gserviceaccount.com, Jul 5 2017 


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

Suspected Commit
  Author : Igor Sheludko
  Commit : 5dd179933c32b0ea992b53b6fc82db0b88a85734
  Date   : Tue Jun 27 15:26:10 2017
  Subject: Reland "[runtime] Make all built-in functions strict."

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_baidu
  Change       : 4.22% | 8386267.42857 -> 8739953.77778

Revision                           Result                  N
chromium@482435                    8386267 +- 804939       14      good
chromium@482701                    8273920 +- 0.0          6       good
chromium@482834                    8332174 +- 494303       9       good
chromium@482851                    8273920 +- 0.0          6       good
chromium@482859                    8273920 +- 0.0          6       good
chromium@482863                    8273920 +- 0.0          6       good
chromium@482864                    8273920 +- 0.0          6       good
chromium@482864,v8@ab028038db      8273920 +- 0.0          6       good
chromium@482864,v8@2ac6dae6fa      8273920 +- 0.0          6       good
chromium@482864,v8@5dd179933c      8798208 +- 0.0          6       bad       <--
chromium@482864,v8@a00eb6833c      8798208 +- 0.0          6       bad
chromium@482865                    8798208 +- 0.0          6       bad
chromium@482867                    8723310 +- 1010433      14      bad
chromium@482900                    8739954 +- 494303       9       bad
chromium@482966                    8739954 +- 494303       9       bad

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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.baidu system_health.memory_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 16 by benhenry@chromium.org, Aug 21 2017

Status: Assigned (was: Untriaged)

Comment 17 by benhenry@chromium.org, Aug 2

Components: Speed>Metrics>SystemHealthRegressions

Comment 18 by benhenry@chromium.org, Aug 2

Components: -Speed>Metrics>SystemHealthRegressions
►

Sign in to add a comment