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

Issue 628252 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.6%-49.1% regression in system_health.memory_desktop at 403879:403951

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@403878  46942635  1506958  12  good
chromium@403951  48183381  1479943  12  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 628252

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_tools-memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_tools_weather
Relative Change: 1.23%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1005
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007147154400643888


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

| 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!
All the failures are on FYI bots. I'm trying to figure out if there's any way to run a bisect on them.

For some reason, this regression only shows on the FYI bot: https://chromeperf.appspot.com/report?sid=3f389feec328b24de1319b621fd8b76e4feaa81d7d2f98c7af7d91745c5f036a&start_rev=402079&end_rev=404911
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jul 16 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@403878  46369536  1184895  12  good
chromium@403951  47602091  1678640  12  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 628252

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_tools-memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_tools_weather
Relative Change: 2.25%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1020
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007063716698714752


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

| 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)
This is a regression on FYI bot(s), for which we currently don't have bisects. Therefore, we agreed to not track Memory System Health benchmarks on FYI bots anymore (https://github.com/catapult-project/catapult/issues/2482).
Labels: SystemHealth-Sheriff
Labels: -Performance-Sheriff

Sign in to add a comment