New issue
Advanced search Search tips

Issue 680680 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.7% regression in system_health.memory_mobile at 442456:442533

Project Member Reported by benjhayden@chromium.org, Jan 12 2017

Issue description

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

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


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

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 12 2017

Cc: napper@chromium.org
Owner: napper@chromium.org

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

Hi napper@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 : napper
  Commit : d8b62ea53246ab528786b9a8d312d0a3733e46e9
  Date   : Tue Jan 10 05:43:57 2017
  Subject: Made text-align property independent.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_social/load_social_pinterest
  Change       : 2.73% | 86112.0 -> 88464.0

Revision             Result              N
chromium@442456      86112.0 +- 0.0      6      good
chromium@442495      86112.0 +- 0.0      6      good
chromium@442498      86112.0 +- 0.0      6      good
chromium@442499      86112.0 +- 0.0      6      good
chromium@442500      88464.0 +- 0.0      6      bad       <--
chromium@442505      88464.0 +- 0.0      6      bad
chromium@442514      88464.0 +- 0.0      6      bad
chromium@442533      88464.0 +- 0.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=load.social.pinterest system_health.memory_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!

Comment 4 by napper@chromium.org, Jan 13 2017

This CL has been reverted. See https://codereview.chromium.org/2627833003

Comment 5 by napper@chromium.org, Jan 13 2017

Status: WontFix (was: Untriaged)
Labels: Performance-Memory

Sign in to add a comment