New issue
Advanced search Search tips

Issue 747239 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1%-8.3% regression in system_health.memory_mobile at 485991:487676

Project Member Reported by mlippautz@chromium.org, Jul 21 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 21 2017

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=747239

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


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

android-nexus5X
android-nexus6
android-nexus7v2
android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 21 2017

Mergedinto: 744354
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Camillo Bruni
  Commit : 36421dc467bffcdcb71967ed39dddca1e33d48c6
  Date   : Wed Jul 12 19:11:04 2017
  Subject: [literals] Disable double lazy boilerplate for literals containing Arrays

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_news/load_news_wikipedia
  Change       : 3.42% | 6057809.14286 -> 6265056.28571

Revision                           Result                  N
chromium@486073                    6057809 +- 170561       14      good
chromium@486174                    6087045 +- 159618       14      good
chromium@486224                    6052637 +- 154689       9       good
chromium@486237                    6077929 +- 89273.6      6       good
chromium@486243                    6059743 +- 19621.6      6       good
chromium@486246                    6025618 +- 119623       6       good
chromium@486248                    6068195 +- 107089       6       good
chromium@486248,v8@42c8df3f46      6062985 +- 107112       6       good
chromium@486248,v8@34874b3b19      6053877 +- 130785       9       good
chromium@486248,v8@36421dc467      6178810 +- 284504       9       bad       <--
chromium@486248,v8@fa4ec9fdbe      6204446 +- 113789       6       bad
chromium@486249                    6211949 +- 272194       9       bad
chromium@486274                    6209275 +- 306050       9       bad
chromium@486474                    6201131 +- 209582       6       bad
chromium@486875                    6199391 +- 156042       6       bad
chromium@487676                    6265056 +- 1012829      14      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.wikipedia 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/8973482719145722880


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment