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

Issue 714006 link

Starred by 1 user
Status: WontFix
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Closed: Apr 2017
Cc:
█ hpayer@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-75.3% regression in system_health.memory_desktop at 461690:461794

Project Member Reported by hpayer@google.com, Apr 21 2017 
See the link to graphs below.

Comment 1 by hpayer@google.com, Apr 21 2017 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgvPf6-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_NS9qQkM


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

android-nexus6
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 21 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : v8-gc-total_max/browse_social/browse_social_twitter


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.twitter v8.runtimestats.browsing_mobile_classic

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

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


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 21 2017 


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : v8-gc-total_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@461694      24.8887 +- 33.6319      21      good
chromium@461778      26.6257 +- 35.9576      21      bad

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.twitter v8.runtimestats.browsing_mobile_classic

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

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


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 22 2017 


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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : v8-gc-total_max/browse_social/browse_social_twitter

Revision             Result                  N
chromium@461694      24.8055 +- 36.0853      21      good
chromium@461778      29.8643 +- 31.131       21      bad

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.twitter v8.runtimestats.browsing_mobile_classic

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

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


| 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 Speed>Bisection.  Thank you!

Comment 8 by hpayer@chromium.org, Apr 24 2017

Status: WontFix (was: Assigned)
Fixed by a revert.
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Apr 30 2017 


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg

Revision             Result                   N
chromium@461689      31459444 +- 1081686      21      good
chromium@461794      31430592 +- 834308       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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop

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

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


| 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 Speed>Bisection.  Thank you!
►

Sign in to add a comment