New issue
Advanced search Search tips

Issue 753969 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

2%-6.8% regression in system_health.memory_mobile at 490644:490729

Project Member Reported by primiano@chromium.org, Aug 9 2017

Issue description

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=0626dc2bd8c32442b90a85876cb589b0a61974dc37c07a40c2d9b9210e2bc864


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

android-nexus5
android-nexus5X
Mergedinto: 750761
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 774a4c5e240569b551cc9d19ae8cac146891d4c4
  Date   : Fri Jul 28 19:42:31 2017
  Subject: Revert "[heap] Reland "[heap] Allow a minimum semi-space size of 512K.""

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_qq
  Change       : 6.86% | 2940051.33333 -> 3141813.33333

Revision                           Result                  N
chromium@490643                    2940051 +- 19326.4      6      good
chromium@490649                    2968931 +- 80006.2      9      good
chromium@490652                    2970141 +- 117288       9      good
chromium@490652,v8@59ddd6061c      2967631 +- 66808.2      9      good
chromium@490652,v8@e567dd3ab4      2945544 +- 524.076      6      good
chromium@490652,v8@774a4c5e24      3078297 +- 221091       6      bad       <--
chromium@490652,v8@4a9718c777      3136205 +- 173879       6      bad
chromium@490653                    3151847 +- 323921       6      bad
chromium@490654                    3174173 +- 296713       6      bad
chromium@490665                    3124788 +- 346617       6      bad
chromium@490686                    3147994 +- 332533       6      bad
chromium@490729                    3141813 +- 143501       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=load.news.qq 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/8971703869829148352


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment