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

Issue 628290 link

Starred by 1 user

Issue metadata

Status: WontFix
Merged: issue 628289
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

16.3%-169.5% regression in system_health.memory_desktop at 404483:404911

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

Issue description

See the link to graphs below.
 
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 14 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@404580  71058074  317086   12  good
chromium@404721  71063770  372346   12  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 628290

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:winheap:effective_size_avg/load_media_soundcloud
Relative Change: 0.08%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2036
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007143261762369328


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

| 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!
Mergedinto: 628289
Status: Duplicate (was: Assigned)
Cc: petrcermak@chromium.org
 Issue 628289  has been merged into this issue.
Status: Assigned (was: Duplicate)
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Jul 15 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@404580  66995868  1386486  12  good
chromium@404721  67563520  1672949  12  bad

Bisect job ran on: win_perf_bisect
Bug ID: 628290

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_tools-memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_tools_docs
Relative Change: 1.73%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6701
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007065080949099120


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

| 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!
Status: WontFix (was: Assigned)
The bisect can't reproduce this on multiple charts. Furthermore, the regression (r404580r404721) came after a symmetrical improvement (r402562r402704). Therefore, I'm going to assume this was due to some infrastructure change and mark this as WontFix.
Labels: SystemHealth-Sheriff
Labels: -Performance-Sheriff

Sign in to add a comment