New issue
Advanced search Search tips

Issue 750695 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Jul 2017
Cc:
perezju@chromium.org
majidvp@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.1%-3065.8% regression in system_health.memory_mobile at 489840:489985

Project Member Reported by majidvp@google.com, Jul 31 2017 
The few metrics where the reference build is also
present it is regression as well. So this may actually
not be a real regression. If bisect does not
turn up anything we should go ahead and close.
Project Member

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

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

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


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

android-nexus5
android-nexus6
android-webview-nexus5X
Project Member

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

Mergedinto: 750299
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Helen Li
  Commit : 73f7cac54a1108eac07d5c7c3367f979a899a0bd
  Date   : Thu Jul 27 14:57:57 2017
  Subject: [wpr-go] Switch system_health_mobile.json to use go

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito
  Change       : 3067.87% | 659642.666667 -> 20896632.0

Revision             Result                    N
chromium@489872      659643 +- 8337.2          6      good
chromium@489901      660294 +- 11825.6         6      good
chromium@489915      657115 +- 2600.39         6      good
chromium@489922      664083 +- 17861.8         6      good
chromium@489923      20910089 +- 55976.2       6      bad       <--
chromium@489924      17537859 +- 18462920      6      bad
chromium@489926      20893956 +- 69207.5       6      bad
chromium@489929      20885989 +- 36566.6       6      bad
chromium@489985      20896632 +- 41731.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.shopping.avito 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/8972540851081687392


For feedback, file a bug with component Speed>Bisection

Comment 4 by majidvp@chromium.org, Jul 31 2017 

This is definitely a real regression. I am seeing a lot of these on android bots.
►

Sign in to add a comment