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

Issue 762221 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
█ briander...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4%-1.7% regression in memory.top_10_mobile at 498042:498105

Project Member Reported by briander...@chromium.org, Sep 5 2017 
See the link to graphs below.
Project Member

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

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

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


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

android-one
Project Member

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


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html

Revision             Result                  N
chromium@498041      24330197 +- 758356      21      good
chromium@498105      24201856 +- 814589      21      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

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 7 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 57c60d68a86bcd9b7dded53d161330b7cd98e5b1
  bad_revision : 4c311cf524efe0e8c9c47d8c3d5159846aa005da

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html

Revision             Result                   N
chromium@497852      23894656 +- 946442       21      good
chromium@497912      23884220 +- 688575       14      good
chromium@497927      23950634 +- 720905       14      good
chromium@497931      24286307 +- 1402794      21      bad
chromium@497934      24280358 +- 1126797      14      bad
chromium@497942      24117983 +- 911719       14      bad
chromium@497973      24116813 +- 879880       14      bad
chromium@498092      24212193 +- 609736       14      bad
chromium@498332      24202538 +- 809583       14      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

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

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


For feedback, file a bug with component Speed>Bisection

Comment 7 by sullivan@chromium.org, Oct 18 2017 

Kicked a bisect on the narrowed range from #5.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Oct 18 2017 


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html
  Change       : 0.64% | 21100988.5714 -> 21226989.3333

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/57c60d68a86bcd9b7dded53d161330b7cd98e5b1..a0f1299665254496f8dec21ad41cfa93cad002dd


Revision             Result                  N
chromium@497927      21100989 +- 102925      14       good
chromium@497928      ---                     ---      build failure
chromium@497929      21131416 +- 124508      14       bad
chromium@497931      21226989 +- 510759      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=http.m.intl.taobao.com.group.purchase.html memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Comment 9 by sullivan@chromium.org, Jan 8 2018

Status: WontFix (was: Untriaged)
These recovered.
►

Sign in to add a comment