New issue
Advanced search Search tips

Issue 717656 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.1% regression in memory.top_10_mobile at 467939:467974

Project Member Reported by nzolghadr@chromium.org, May 2 2017

Issue description

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

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


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

android-nexus5X
Mergedinto: 717402
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : delphick
  Commit : c41d3c785c5179a38e54c6c80ea63d56cc7cfd12
  Date   : Fri Apr 28 11:50:09 2017
  Subject: Restore one millisecond minimum timeout for setTimeout.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 1.09% | 162171.555556 -> 163736.0

Revision             Result                 N
chromium@467938      162172 +- 1659.34      9       good
chromium@467956      162479 +- 2974.94      14      good
chromium@467961      161976 +- 0.0          6       good
chromium@467962      163736 +- 0.0          6       bad       <--
chromium@467963      163736 +- 0.0          6       bad
chromium@467965      163736 +- 0.0          6       bad
chromium@467974      163736 +- 0.0          9       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 memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980681756643265840

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6101385147318272


| 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!

Sign in to add a comment