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

Issue 862979 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 856027
Owner:
Closed: Jul 17
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1% improvement in memory.top_10_mobile at 1529486895:1529498741

Project Member Reported by perezju@google.com, Jul 12

Issue description

Want to figure out cause of this improvement.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=862979

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


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

health-plan-clankium-phone

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 0.69% | 64268196.4444 -> 63823097.7778

Revision                                       Result                  N
android-chrome@dff611cf06                      64268196 +- 247758      9      good
android-chrome@bfbc254ab1                      64302557 +- 238448      6      good
android-chrome@bfbc254ab1,chromium@568669      63867699 +- 118534      6      bad
android-chrome@3447e60a36                      63823098 +- 228182      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.en.m.wikipedia.org.wiki.Science 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/8941211512140509024


For feedback, file a bug with component Speed>Bisection
Cc: sigurds@chromium.org
Owner: sigurds@chromium.org
Status: Assigned (was: Untriaged)

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

Hi sigurds@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 : Sigurd Schneider
  Commit : f5a8352b0fbba0d88104de7949a0d0c238765cf8
  Date   : Tue Jun 19 11:39:09 2018
  Subject: [embedded-builtins] Enable on all arches except x86 for benchmarks

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 0.65% | 64254543.1111 -> 63830152.0

Revision                                                     Result                   N
android-chrome@bfbc254ab1                                    64254543 +- 89749.2      9       good
android-chrome@bfbc254ab1,chromium@568638                    64176264 +- 218034       14      good
android-chrome@bfbc254ab1,chromium@568654                    64236339 +- 236524       9       good
android-chrome@bfbc254ab1,chromium@568654,v8@38bec2eadc      64308701 +- 187625       6       good
android-chrome@bfbc254ab1,chromium@568654,v8@f5a8352b0f      63759155 +- 215037       6       bad       <--
android-chrome@bfbc254ab1,chromium@568655                    63873160 +- 242279       9       bad
android-chrome@bfbc254ab1,chromium@568656                    63848129 +- 243681       9       bad
android-chrome@bfbc254ab1,chromium@568658                    63814451 +- 196790       6       bad
android-chrome@bfbc254ab1,chromium@568661                    63811720 +- 216833       6       bad
android-chrome@bfbc254ab1,chromium@568669                    63877711 +- 171488       9       bad
android-chrome@3447e60a36                                    63830152 +- 192115       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.en.m.wikipedia.org.wiki.Science 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/8940850286411471376


For feedback, file a bug with component Speed>Bisection
Mergedinto: 856027
Status: Duplicate (was: Assigned)

Sign in to add a comment