New issue
Advanced search Search tips

Issue 763913 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

3.4%-6.4% regression in system_health.memory_mobile 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=763913

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


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

android-one
chromium-rel-win7-dual
Project Member

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

Cc: jkummerow@chromium.org
Owner: jkummerow@chromium.org
Status: Assigned (was: Untriaged)

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

Hi jkummerow@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 : Jakob Kummerow
  Commit : cfcdeab0028b7f27fff277adfef602776aeeb37b
  Date   : Tue Sep 05 18:00:39 2017
  Subject: [storeic] Drop duplicate stubs for each LanguageMode

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social/browse_social_pinterest_infinite_scroll
  Change       : 0.50% | 21676587.5556 -> 21568951.1111

Revision                           Result                   N
chromium@499765                    21676588 +- 57787.5      9       good
chromium@499794                    21682502 +- 60259.1      9       good
chromium@499808                    21665288 +- 223749       14      good
chromium@499812                    21672603 +- 191888       14      good
chromium@499813                    21680325 +- 83808.9      9       good
chromium@499813,v8@fbd1d1ad25      21668760 +- 97357.8      14      good
chromium@499813,v8@62fee3b64c      21655373 +- 350073       21      good
chromium@499813,v8@cfcdeab002      21604920 +- 248401       14      bad       <--
chromium@499813,v8@1400544c37      21605604 +- 223980       14      bad
chromium@499814                    21605297 +- 222446       14      bad
chromium@499815                    21603655 +- 201865       9       bad
chromium@499822                    21607798 +- 84821.6      9       bad
chromium@499878                    21568951 +- 328657       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 --story-filter=browse.social.pinterest.infinite.scroll 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/8968743553640633264


For feedback, file a bug with component Speed>Bisection
Project Member

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

 Issue 763920  has been merged into this issue.
Status: WontFix (was: Assigned)
Go home, bisect bot, you're drunk. 21.60MB is less than 21.65MB, so this is an improvement. I'm not gonna revert the CL that caused that improvement.

Sign in to add a comment