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

Issue 631054 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 631048
Owner:
Last visit > 30 days ago
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

46.3% regression in system_health.memory_desktop at 407389:407390

Project Member Reported by petrcermak@chromium.org, Jul 25 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=631054

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2qWQoAkM


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

chromium-rel-mac11
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 25 2016


===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@407388  4391675  663445   12  good
chromium@407390  4838555  0.0      8   bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 631054

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:media:effective_size_avg/load_media_youtube
Relative Change: 20.32%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/761
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006153077847666208


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5292867367469056

| 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 Tests>AutoBisect.  Thank you!
Lets try another bisect.
Mergedinto: 631048
Status: Duplicate (was: Assigned)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : [system-health] Tear down the browser after each story in system_health.memory_*
Author  : petrcermak
Commit description:
  
Rationale: Each story should be completely independent as it will allow
us to compare the results from individual stories. As a result, it will
be possible to compare/subtract the results from, e.g.
LOAD:social:facebook and BROWSE:social:facebook.

More importantly, there are literally hundreds of perf dashboard alerts
each time we add a story to the SH story set. This should fix that.

*** NOTE TO PERF SHERIFF ***
This patch will definitely cause a lot of improvements and/or
regressions in system_health.memory_desktop and
system_health.memory_mobile benchmarks. This is expected.

BUG=589726
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

Review-Url: https://codereview.chromium.org/2161363004
Cr-Commit-Position: refs/heads/master@{#407380}
Commit  : a30a0719cdc625d240ba75054fc0de1b9f826625
Date    : Sun Jul 24 12:32:33 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@407200  3306395  0.0      5  good
chromium@407350  3408539  139866   5  good
chromium@407369  3357467  114200   5  good
chromium@407379  3338315  90283.4  8  good
chromium@407380  4072475  699332   5  bad    <--
chromium@407381  4487435  653720   8  bad
chromium@407382  4583195  571002   5  bad
chromium@407384  4583195  571002   5  bad
chromium@407388  4583195  571002   5  bad
chromium@407425  4838555  0.0      5  bad
chromium@407500  4838555  0.0      5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 631054

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:media:effective_size_avg/load_media_youtube
Relative Change: 46.34%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/791
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005516011015801152


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5800657081073664

| 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 Tests>AutoBisect.  Thank you!
Labels: SystemHealth-Sheriff
Labels: -Performance-Sheriff

Sign in to add a comment