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

Issue 636727 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

1.6% regression in system_health.memory_mobile at 408608:408617

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

Issue description

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 12 2016

Mergedinto: 633230
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Framework for indexing of subresource filtering rules.
Author  : engedy
Commit description:
  
Make the RulesetService capable of receiving and indexing Safe Browsing
subresource filtering rules coming in through the component updater. The wire
format is still TBD, but for now consists of a single rule.

Also, change the directory structure so that both indexed and unindexed rules
are stored under a BASE directory at "$USER_DATA_DIR/Subresource Filter/".
Unindexed rules are now stored under "$BASE/Unindexed Rules/$CONTENT_VERSION/";
and indexed rules under "$BASE/Indexed Rules/$FORMAT_VERSION/$CONTENT_VERSION",
instead of "$BASE/$FORMAT_VERSION_$CONTENT_VERSION".

Furthermore, refactor TestRulesetCreator to facilitate testing by supplying
both the indexed/unindexed representation of the testing rules, and making them
available as files, file paths or blobs.

BUG=609747

Review-Url: https://codereview.chromium.org/2182493009
Cr-Commit-Position: refs/heads/master@{#408615}
Commit  : 6cfa34f00f9631c99f8540188e9a5aab7502eebe
Date    : Fri Jul 29 11:20:01 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@408607  1817805  6730.41  5  good
chromium@408612  1815347  8879.92  5  good
chromium@408614  1812890  6211.89  5  good
chromium@408615  1836646  4670.16  5  bad    <--
chromium@408617  1839104  5792.62  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 636727

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_tools-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:private_dirty_size_avg/load_tools_weather
Relative Change: 1.17%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3976
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004635448098716368


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

| 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

Sign in to add a comment