Issue metadata
Sign in to add a comment
|
Improvements from removing next field from JS functions |
||||||||||||||||||||||||
Issue descriptionBisect of memory improvements.
,
Sep 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968465104495681840
,
Sep 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968464540116123408
,
Sep 14 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : xunjieli Commit : 724bb776bcdea642a5bc9cc20fe14bb0282b4900 Date : Wed Sep 06 14:29:20 2017 Subject: [Telemetry] Use --ignore-certificate-errors-spki-list to bypass cert errors Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_social/load_social_vk Change : 5.40% | 32425614.6667 -> 30673438.0 Revision Result N chromium@500342 32425615 +- 1476181 6 good chromium@500344 32849469 +- 429871 6 good chromium@500344,catapult@c5a474f50f 32431512 +- 1503892 6 good chromium@500344,catapult@724bb776bc 30614671 +- 488123 6 bad <-- chromium@500344,catapult@80c47581b1 30543819 +- 567065 6 bad chromium@500344,catapult@4f611510b9 30682251 +- 247048 6 bad chromium@500344,catapult@442f46edf7 30655049 +- 369242 6 bad chromium@500345 30622867 +- 354569 6 bad chromium@500348 30560923 +- 274214 6 bad chromium@500354 30645547 +- 584217 6 bad chromium@500366 30641892 +- 397529 6 bad chromium@500389 30706975 +- 171906 6 bad chromium@500435 30673438 +- 410157 6 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.vk 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/8968470055714521376 For feedback, file a bug with component Speed>Bisection
,
Sep 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: linux_perf_bisect Benchmark : smoothness.top_25_smooth Metric : percentage_smooth/https___mail.google.com_mail_ Revision Result N chromium@500317 50.2258 +- 11.0318 21 good chromium@500432 51.525 +- 15.9914 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=https...mail.google.com.mail. smoothness.top_25_smooth More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968465104495681840 For feedback, file a bug with component Speed>Bisection
,
Sep 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968457052883194736
,
Sep 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968456683080038256
,
Sep 14 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : nednguyen Commit : aca6ca9eacf53d6d12f599ba6b9011951fde2017 Date : Mon Sep 11 16:56:48 2017 Subject: Use --ignore-certificate-errors for webview Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : Parse:duration_avg/browse_news/browse_news_cricbuzz Change : 631.12% | 84.5038333333 -> 617.826666667 Revision Result N chromium@500984 84.5038 +- 9.41991 6 good chromium@501011 92.972 +- 12.6386 6 good chromium@501011,catapult@59c0f71abc 92.3432 +- 11.1165 6 good chromium@501011,catapult@0ed6f7d08a 90.88 +- 5.8076 6 good chromium@501011,catapult@aca6ca9eac 587.247 +- 110.979 6 bad <-- chromium@501012 596.687 +- 121.125 6 bad chromium@501013 600.207 +- 99.9155 6 bad chromium@501015 624.987 +- 124.88 6 bad chromium@501018 585.979 +- 47.8303 6 bad chromium@501024 639.659 +- 88.6407 6 bad chromium@501037 597.155 +- 92.9244 6 bad chromium@501089 617.827 +- 128.907 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cricbuzz v8.runtimestats.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968464540116123408 For feedback, file a bug with component Speed>Bisection
,
Sep 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968454788187314336
,
Sep 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background_social/background_social_facebook Revision Result N chromium@500243 4704897 +- 700007 21 good chromium@500451 4690734 +- 730331 21 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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.social.facebook system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968456683080038256 For feedback, file a bug with component Speed>Bisection
,
Sep 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: win_x64_perf_bisect Benchmark : v8.browsing_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_search/browse_search_google Revision Result N chromium@500368 13167053 +- 1186336 21 good chromium@500482 13029388 +- 1198437 21 bad 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=browse.search.google v8.browsing_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968457052883194736 For feedback, file a bug with component Speed>Bisection
,
Sep 14 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Juliana Franco Commit : f82ae284fa2b1724e3dc2df7f4dd8ffc819800c2 Date : Thu Sep 07 12:36:49 2017 Subject: Remove the next field from JS functions. Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background_social/background_social_facebook Change : 3.67% | 4741189.33333 -> 4567330.0 Revision Result N chromium@500243 4741189 +- 413110 9 good chromium@500347 4825943 +- 55629.6 6 good chromium@500399 4789697 +- 349275 9 good chromium@500425 4744919 +- 503684 14 good chromium@500426 4779320 +- 335756 9 good chromium@500426,v8@7b53a0e010 4815154 +- 4665.66 6 good chromium@500426,v8@f82ae284fa 4446189 +- 17829.5 6 bad <-- chromium@500426,v8@e67420cbc2 4509689 +- 320652 6 bad chromium@500426,v8@357269a5d9 4572064 +- 489339 9 bad chromium@500427 4515110 +- 317047 6 bad chromium@500429 4505168 +- 322008 6 bad chromium@500432 4561580 +- 756840 21 bad chromium@500438 4542905 +- 533872 14 bad chromium@500451 4567330 +- 401441 6 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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.social.facebook system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968454788187314336 For feedback, file a bug with component Speed>Bisection
,
Sep 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968391350058190704
,
Sep 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968391272511290304
,
Sep 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968391175785135312
,
Sep 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968391127896763904
,
Sep 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968391011388827168
,
Sep 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968390943866472272
,
Sep 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968390914090793504
,
Sep 15 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: win_x64_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_news/browse_news_reddit Change : 1.49% | 12212743.619 -> 12030835.4286 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/fbc9c1b99ba5c1e08fc1e70cbb449c5159b2216c..2c3ed3645a66024432c193e62e1ad792f7a3b94f Revision Result N chromium@500368 12212744 +- 665950 21 good chromium@500425 12290798 +- 1437744 21 good chromium@500426 --- --- build failure chromium@500427 12103245 +- 1035830 14 bad chromium@500428 12064942 +- 848636 14 bad chromium@500433 12094452 +- 617708 14 bad chromium@500440 12049532 +- 1219764 9 bad chromium@500454 12110237 +- 716416 21 bad chromium@500482 12030835 +- 594630 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=browse.news.reddit 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/8968391175785135312 For feedback, file a bug with component Speed>Bisection
,
Sep 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : xunjieli Commit : 724bb776bcdea642a5bc9cc20fe14bb0282b4900 Date : Wed Sep 06 14:29:20 2017 Subject: [Telemetry] Use --ignore-certificate-errors-spki-list to bypass cert errors Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/long_running_tools/long_running_tools_gmail-foreground Change : 52.24% | 3345464.0 -> 1597837.33333 Revision Result N chromium@500323 3345464 +- 0.0 9 good chromium@500334 3345464 +- 0.0 6 good chromium@500340 2995939 +- 1914429 6 good chromium@500343 3345464 +- 0.0 6 good chromium@500344 3345464 +- 0.0 6 good chromium@500344,catapult@c5a474f50f 3345464 +- 0.0 6 good chromium@500344,catapult@724bb776bc 1248312 +- 0.0 6 bad <-- chromium@500344,catapult@80c47581b1 1248312 +- 0.0 6 bad chromium@500344,catapult@4f611510b9 1248312 +- 0.0 6 bad chromium@500344,catapult@442f46edf7 1481329 +- 1977214 9 bad chromium@500345 1248312 +- 0.0 6 bad chromium@500367 1597837 +- 1914429 6 bad chromium@500410 1248312 +- 0.0 6 bad chromium@500497 1597837 +- 1914429 6 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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=long.running.tools.gmail.foreground system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968390943866472272 For feedback, file a bug with component Speed>Bisection
,
Sep 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Juliana Franco Commit : f82ae284fa2b1724e3dc2df7f4dd8ffc819800c2 Date : Thu Sep 07 12:36:49 2017 Subject: Remove the next field from JS functions. Bisect Details Configuration: linux_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social/browse_social_twitter Change : 1.19% | 24424248.0 -> 24133396.4444 Revision Result N chromium@500317 24424248 +- 572003 9 good chromium@500375 24480073 +- 32116.0 6 good chromium@500404 24486620 +- 61886.1 6 good chromium@500418 24505177 +- 49017.1 6 good chromium@500425 24470483 +- 49170.4 6 good chromium@500426 24412321 +- 619093 9 good chromium@500426,v8@7b53a0e010 24430258 +- 599745 9 good chromium@500426,v8@f82ae284fa 24139988 +- 48511.7 9 bad <-- chromium@500426,v8@e67420cbc2 24126233 +- 43768.4 9 bad chromium@500426,v8@357269a5d9 24064170 +- 547531 9 bad chromium@500427 24126511 +- 36174.5 6 bad chromium@500429 24123221 +- 21160.1 6 bad chromium@500432 24133396 +- 72575.9 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter 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/8968391272511290304 For feedback, file a bug with component Speed>Bisection
,
Sep 15 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_nexus5_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_tools/load_tools_weather Change : 64.09% | 5410450.66667 -> 1942853.77778 Suspected Commit Range 2 commits in range Unknown depot, please contact team to have this added. Revision Result N chromium@500323 5410451 +- 1164966 9 good chromium@500339 5548325 +- 4041.45 6 good chromium@500343 5549492 +- 0.0 6 good chromium@500344 3369453 +- 7945220 14 good chromium@500344,catapult@80c47581b1 3562633 +- 8009007 14 good chromium@500344,catapult@fc8c846a47 --- --- build failure chromium@500344,catapult@4f611510b9 1387576 +- 1878774 14 bad chromium@500345 1834067 +- 5376047 14 bad chromium@500347 1726221 +- 4055191 9 bad chromium@500355 2192248 +- 5298365 9 bad chromium@500387 1898211 +- 3559642 6 bad chromium@500451 2587785 +- 7027686 14 bad chromium@500579 1942854 +- 4237920 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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.weather system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968391011388827168 For feedback, file a bug with component Speed>Bisection
,
Sep 15 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: win_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_games/load_games_miniclip Change : 2.35% | 14252603.7143 -> 14044168.2857 Suspected Commit Range 3 commits in range https://chromium.googlesource.com/chromium/src/+log/7877850aacaead4be004d301b876ac556a48a7ab..e7d66efe5dd9396bc97569640704f33202edef6e Revision Result N chromium@500421 14252604 +- 1558902 14 good chromium@500426 14239685 +- 1588276 14 good chromium@500427 --- --- build failure chromium@500428 --- --- build failure chromium@500429 14065246 +- 1483527 14 bad chromium@500431 14061771 +- 1831042 21 bad chromium@500441 14024081 +- 1799666 21 bad chromium@500467 13872997 +- 1060867 14 bad chromium@500504 14044168 +- 1492037 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.miniclip 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/8968391127896763904 For feedback, file a bug with component Speed>Bisection
,
Sep 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : xunjieli Commit : 724bb776bcdea642a5bc9cc20fe14bb0282b4900 Date : Wed Sep 06 14:29:20 2017 Subject: [Telemetry] Use --ignore-certificate-errors-spki-list to bypass cert errors Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/long_running_tools/long_running_tools_gmail-foreground Change : 62.69% | 3345464.0 -> 1248312.0 Revision Result N chromium@500323 3345464 +- 0.0 9 good chromium@500334 3345464 +- 0.0 9 good chromium@500340 3345464 +- 0.0 9 good chromium@500343 3345464 +- 0.0 9 good chromium@500344 3345464 +- 0.0 9 good chromium@500344,catapult@c5a474f50f 3345464 +- 0.0 9 good chromium@500344,catapult@724bb776bc 1597837 +- 1914429 6 bad <-- chromium@500344,catapult@80c47581b1 1732270 +- 3185803 13 bad chromium@500344,catapult@4f611510b9 1481329 +- 1977214 9 bad chromium@500344,catapult@442f46edf7 1847498 +- 3544834 14 bad chromium@500345 1714346 +- 2615608 9 bad chromium@500367 1481329 +- 1977214 9 bad chromium@500410 1248312 +- 0.0 6 bad chromium@500497 1248312 +- 0.0 6 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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=long.running.tools.gmail.foreground system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8968390914090793504 For feedback, file a bug with component Speed>Bisection
,
Sep 15 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: linux_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_news/load_news_cnn Change : 0.89% | 52344292.0 -> 51876345.7778 Suspected Commit Range 29 commits in range https://chromium.googlesource.com/chromium/src/+log/c1e78ddc9261456d3fda586702143bc10efa207b..bf74aebd5654cf9d272bf890b093238bbd5c89bf Revision Result N chromium@500317 52344292 +- 1251853 14 good chromium@500375 52623160 +- 1192377 14 good chromium@500376 --- --- build failure --- --- --- too many build failures to list chromium@500403 --- --- build failure chromium@500404 52524390 +- 2802936 14 bad chromium@500432 51876346 +- 2621435 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.cnn 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/8968391350058190704 For feedback, file a bug with component Speed>Bisection
,
Sep 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968197431830596032
,
Sep 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968197411022481408
,
Sep 17 2017
=== BISECT JOB RESULTS ===
Bisect failed unexpectedly
Bisect was aborted with the following:
Step('Bisecting revision.buildbucket.put (3)') failed with return_code 1
Bisect Details
Configuration: mac_10_12_mini_8gb_perf_bisect
Benchmark : system_health.memory_desktop
Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_media/load_media_9gag
Revision Result N
chromium@500407 43719133 +- 1196092 14 good
chromium@500420 43852644 +- 1070664 6 good
chromium@500426 43892079 +- 1035218 9 good
chromium@500426,v8@7b53a0e010 43905909 +- 715428 6 good
chromium@500426,v8@357269a5d9 43205265 +- 541514 6 bad
chromium@500427 43066303 +- 970307 6 bad
chromium@500428 43130151 +- 1074122 9 bad
chromium@500429 43138628 +- 502414 9 bad
chromium@500432 43270948 +- 640128 14 bad
chromium@500457 43151680 +- 989993 14 bad
chromium@500506 43017548 +- 965960 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.9gag 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/8968197431830596032
For feedback, file a bug with component Speed>Bisection
,
Sep 18 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Juliana Franco Commit : f82ae284fa2b1724e3dc2df7f4dd8ffc819800c2 Date : Thu Sep 07 12:36:49 2017 Subject: Remove the next field from JS functions. Bisect Details Configuration: mac_10_12_mini_8gb_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_news/load_news_cnn Change : 1.53% | 52648591.1111 -> 51841506.6667 Revision Result N chromium@500407 52648591 +- 962760 9 good chromium@500420 53120196 +- 2378051 6 good chromium@500426 52849910 +- 1978701 9 good chromium@500426,v8@7b53a0e010 52459879 +- 639459 6 good chromium@500426,v8@f82ae284fa 51738661 +- 1036449 9 bad <-- chromium@500426,v8@e67420cbc2 51538579 +- 646313 6 bad chromium@500426,v8@357269a5d9 51620555 +- 517818 6 bad chromium@500427 51737515 +- 2123147 14 bad chromium@500428 51803630 +- 2296048 14 bad chromium@500429 51585839 +- 797844 9 bad chromium@500432 51598045 +- 770142 6 bad chromium@500457 51917241 +- 1001812 6 bad chromium@500506 51841507 +- 966098 6 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.cnn 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/8968197411022481408 For feedback, file a bug with component Speed>Bisection
,
Sep 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968126875740869424
,
Sep 18 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Juliana Franco Commit : f82ae284fa2b1724e3dc2df7f4dd8ffc819800c2 Date : Thu Sep 07 12:36:49 2017 Subject: Remove the next field from JS functions. Bisect Details Configuration: linux_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_media/load_media_youtube Change : 0.79% | 16632556.0 -> 16500725.3333 Revision Result N chromium@500317 16632556 +- 120888 6 good chromium@500375 16683343 +- 28110.2 6 good chromium@500404 16691181 +- 35576.7 6 good chromium@500418 16679303 +- 8495.33 6 good chromium@500425 16681205 +- 29087.0 6 good chromium@500426 16678440 +- 14547.0 6 good chromium@500426,v8@7b53a0e010 16699860 +- 110508 6 good chromium@500426,v8@f82ae284fa 16501359 +- 10990.3 6 bad <-- chromium@500426,v8@e67420cbc2 16510629 +- 38354.5 6 bad chromium@500426,v8@357269a5d9 16504196 +- 7418.33 6 bad chromium@500427 16498380 +- 15670.8 6 bad chromium@500429 16510628 +- 27650.2 6 bad chromium@500432 16500725 +- 6001.28 6 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.youtube 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/8968126875740869424 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 14 2017