New issue
Advanced search Search tips

Issue 739308 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 738834
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.5% regression in system_health.memory_mobile at 483183:483311

Project Member Reported by rmcilroy@chromium.org, Jul 5 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=739308

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7r-t6AoM


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

android-nexus5
Mergedinto: 738834
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : tzik
  Commit : 211d6bc6aacfeed4aa730418801c86c7cef6719c
  Date   : Thu Jun 29 04:19:13 2017
  Subject: Notify RendererScheduler of starting LOADING phase on DidStartProvisionalLoad

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_cnn
  Change       : 11.46% | 34039528.0 -> 37938920.0

Revision             Result               N
chromium@483182      34039528 +- 0.0      6      good
chromium@483247      34039528 +- 0.0      6      good
chromium@483279      34039528 +- 0.0      6      good
chromium@483287      34039528 +- 0.0      6      good
chromium@483291      34039528 +- 0.0      6      good
chromium@483293      34039528 +- 0.0      6      good
chromium@483294      34039528 +- 0.0      6      good
chromium@483295      37938920 +- 0.0      6      bad       <--
chromium@483311      37938920 +- 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=browse.news.cnn 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/8974917638678032432


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment