Issue metadata
Sign in to add a comment
|
5.5% regression in system_health.memory_mobile at 454643:454700 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985647931042722800
,
Mar 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/browse_news/browse_news_nytimes Revision Result N chromium@454642 167461549 +- 30129477 21 good chromium@454700 167442337 +- 33367846 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=browse.news.nytimes system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985647931042722800 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5910827317592064 | 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!
,
Mar 15 2017
This kind of recovers but is a bit noisy so it's hard to tell. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by benhenry@google.com
, Mar 8 2017