New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 692944 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.2% regression in system_health.memory_mobile at 450255:450284

Project Member Reported by alexclarke@chromium.org, Feb 16 2017

Issue description

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

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 16 2017

Cc: yosin@chromium.org
Owner: yosin@chromium.org

=== Auto-CCing suspected CL author yosin@chromium.org ===

Hi yosin@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : yosin
  Commit : 17c84b2b6519c821dc319e79f2a7a4508508e20f
  Date   : Tue Feb 14 06:34:37 2017
  Subject: Make FrameSelection to hold non-canonicalized DOM positions

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_news/load_news_nytimes
  Change       : 1.15% | 547168.0 -> 553450.666667

Revision             Result                 N
chromium@450254      547168 +- 997.661      6      good
chromium@450269      546747 +- 779.141      6      good
chromium@450277      547035 +- 1033.37      6      good
chromium@450279      547035 +- 1033.37      6      good
chromium@450280      553584 +- 0.0          6      bad       <--
chromium@450281      553451 +- 730.297      6      bad
chromium@450284      553451 +- 730.297      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.nytimes system_health.memory_mobile

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

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


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

Comment 4 by yosin@chromium.org, Feb 16 2017

 Issue 692941  has been merged into this issue.

Comment 5 by yosin@chromium.org, Feb 16 2017

Status: Started (was: Untriaged)
Investigating...
Mergedinto: 692537
Status: Duplicate (was: Started)
Labels: Performance-Memory
Labels: -Performance-Memory

Sign in to add a comment