Issue metadata
Sign in to add a comment
|
1% regression in memory.top_10_mobile at 442265:442305 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990565055696768928
,
Jan 13 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_mobile_twitter_com_justinbieber_skip_interstitial_true Revision Result N chromium@442265 2409454 +- 38695.0 21 good chromium@442305 2412288 +- 26636.7 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=https.mobile.twitter.com.justinbieber.skip.interstitial.true memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8990565055696768928 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5802736639016960 | 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 Tests>AutoBisect. Thank you!
,
Jan 20 2017
,
Jan 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989548103080971472
,
Jan 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : mvstanton Commit : 38602f1ff553b32815d34a05cd6d965f4fc20960 Date : Mon Jan 09 15:31:00 2017 Subject: [FeedbackVector] Infrastructure for literal arrays in the vector. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_mobile_twitter_com_justinbieber_skip_interstitial_true Change : 0.49% | 2392817.33333 -> 2404653.33333 Revision Result N chromium@442231 2392817 +- 2201.16 6 good chromium@442279 2391704 +- 7488.48 6 good chromium@442303 2391704 +- 7488.48 6 good chromium@442309 2391701 +- 7485.54 6 good chromium@442312 2391687 +- 7469.63 6 good chromium@442312,v8@e7fc42796c 2391704 +- 7488.48 6 good chromium@442312,v8@38602f1ff5 2404203 +- 7478.24 6 bad <-- chromium@442313 2404203 +- 7347.57 6 bad chromium@442314 2406997 +- 18277.8 6 bad chromium@442315 2404223 +- 7368.69 6 bad chromium@442327 2404651 +- 7364.32 6 bad chromium@442422 2404653 +- 7367.41 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989548103080971472 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5854860865437696 | 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 Tests>AutoBisect. Thank you!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982580328453913008 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nzolghadr@chromium.org
, Jan 13 2017