New issue
Advanced search Search tips

Issue 763915 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

2% regression in system_health.memory_desktop at 498790:500334

Project Member Reported by jgruber@chromium.org, Sep 11 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 11 2017

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

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


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

chromium-rel-win7-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 11 2017

Mergedinto: 762492
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Marja Hölttä
  Commit : 36d703778ccd0d2777e0d4b69ed6e65e39a9f521
  Date   : Mon Sep 04 16:05:39 2017
  Subject: [parser] Tentatively enable FLAG_preparser_scope_analysis.

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 2.23% | 18785502.6667 -> 19205329.6

Revision                           Result                   N
chromium@498789                    18785503 +- 66798.2      6      good
chromium@499176                    18764576 +- 40141.1      6      good
chromium@499369                    18766502 +- 36091.0      6      good
chromium@499466                    18754262 +- 57392.3      6      good
chromium@499514                    18789996 +- 65635.9      6      good
chromium@499538                    18739415 +- 50979.2      6      good
chromium@499538,v8@1c1457fa70      18750373 +- 82512.4      6      good
chromium@499538,v8@36d703778c      19205142 +- 53104.4      6      bad       <--
chromium@499538,v8@7abdadca0e      19213469 +- 43367.7      6      bad
chromium@499539                    19199485 +- 68699.9      6      bad
chromium@499540                    19194753 +- 60762.2      6      bad
chromium@499541                    19195751 +- 63575.8      6      bad
chromium@499544                    19206741 +- 66909.4      6      bad
chromium@499550                    19206036 +- 37409.6      6      bad
chromium@499562                    19198119 +- 67738.4      6      bad
chromium@500334                    19205330 +- 52638.1      5      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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook.infinite.scroll system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968743236927552480


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment