Issue metadata
Sign in to add a comment
|
2.9%-89.3% regression in top_10_mobile_memory_ignition at 405027:405107 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 14 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007175413817202896
,
Jul 14 2016
,
Jul 14 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007172822044759168
,
Jul 14 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007172813669140240
,
Jul 14 2016
,
Jul 14 2016
We recorded new wpr for all the pages in top_10_mobile_memory (https://codereview.chromium.org/2138133003/). This was done to fix google.com redirection problem (see this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=617914) All the pages were updated instead of only google because memory infra people (perezju@) felt it is better to update all of them. Since these are new set of pages, there would be variation in the results.
,
Jul 14 2016
,
Jul 14 2016
=== Auto-CCing suspected CL author mythria@chromium.org === Hi mythria@chromium.org, the bisect results pointed to your CL below as possibly causing a regression. Please have a look at this info and see whether your CL be related. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [perf] Change google.com to google.co.uk in top_10_mobile_memory and dual_browser page sets. Author : mythria Commit description: In the top10_mobile page set google.com gets redirected to google.ca. This sometimes causes problems in telemetry with scrolling. As a short term fix, replace google.com with google.co.uk in the page set. We cannot change it to google.ca because memory_top_10_mobile uses the same page set but with a different wpr that has a recording of google.co.uk. Updated dual_browser page set to be consistent with top_10_mobile page set. Also recorded new wprs for memory_top_10_mobile, dual_browser and top_10_mobile_memory. BUG= chromium:617914 LOG=N CQ_INCLUDE_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq Review-Url: https://codereview.chromium.org/2138133003 Cr-Commit-Position: refs/heads/master@{#405099} Commit : c5acd3851a2f34de15dd89119f0be48c22a9aa72 Date : Wed Jul 13 09:04:39 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@405074 6080747 147529 5 good chromium@405087 6020611 159644 5 good chromium@405094 6196471 19334.8 5 good chromium@405097 6190486 10244.1 5 good chromium@405098 6189938 5893.98 5 good chromium@405099 11186130 88327.1 5 bad <-- chromium@405100 11259303 64658.3 5 bad Bisect job ran on: android_one_perf_bisect Bug ID: 628120 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory_ignition Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_max/https___m.facebook.com_rihanna Relative Change: 85.16% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1410 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007175413817202896 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5550103327145984 | 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!
,
Jul 14 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@405048 7330020 339089 18 good chromium@405052 7446528 0.0 18 bad Bisect job ran on: win_8_perf_bisect Bug ID: 628120 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory_ignition Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_max/http___www.baidu.com_s?word_google Relative Change: 2.90% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2033 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007172813669140240 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5583688897658880 | 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! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hablich@chromium.org
, Jul 14 2016