New issue
Advanced search Search tips

Issue 633229 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.3%-1.9% regression in system_health.memory_mobile at 408603:408621

Project Member Reported by petrcermak@chromium.org, Aug 1 2016

Issue description

See the link to graphs below.
 

===== 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@408611  368634  4435.39  8  good
chromium@408613  372444  418.607  8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 633229

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_media_dailymotion
Relative Change: 0.62%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3129
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005518807598115616


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

| 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!
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Aug 16 2016

Cc: lizeb@chromium.org
Owner: lizeb@chromium.org

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

Hi lizeb@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : predictors: Support fonts in resource_prefetch_predictors.
Author  : lizeb
Commit description:
  
BUG=631966

Review-Url: https://codereview.chromium.org/2184323003
Cr-Commit-Position: refs/heads/master@{#408613}
Commit  : f513f1db12aa282b38f3d2624b792af7626b1f5b
Date    : Fri Jul 29 10:54:50 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@408602  367382  2308.04  5  good
chromium@408608  367856  1674.43  5  good
chromium@408611  366435  529.501  5  good
chromium@408612  366672  2050.75  5  good
chromium@408613  372355  529.501  5  bad    <--

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 633229

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_media-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_media_dailymotion
Relative Change: 1.35%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3205
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004246995625841120


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

| 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!

Comment 7 by lizeb@chromium.org, Aug 17 2016

Status: Started (was: Assigned)
Project Member

Comment 8 by bugdroid1@chromium.org, Aug 18 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a95e28ff66d50d199f6c63cc6b8c3094a3787ca2

commit a95e28ff66d50d199f6c63cc6b8c3094a3787ca2
Author: lizeb <lizeb@chromium.org>
Date: Thu Aug 18 09:19:39 2016

Remove obsolete SpeculativeResourcePrefetching trial from fieldtrial_testing_config_android.json.

BUG=633185, 633229 

Review-Url: https://codereview.chromium.org/2253073002
Cr-Commit-Position: refs/heads/master@{#412774}

[modify] https://crrev.com/a95e28ff66d50d199f6c63cc6b8c3094a3787ca2/testing/variations/fieldtrial_testing_config_android.json

Comment 9 by lizeb@chromium.org, Aug 18 2016

Status: WontFix (was: Started)
WontFix (or fixed, depending how you look at it), since the experiment has been removed from the perf bots.

lizeb: Thanks a lot for sorting this out :-)
Labels: SystemHealth-Sheriff
Labels: -Performance-Sheriff

Sign in to add a comment