New issue
Advanced search Search tips

Issue 629212 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 628120
Owner:
Closed: Jul 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.8% regression in top_10_mobile_memory at 405070:405136

Project Member Reported by m...@chromium.org, Jul 18 2016

Issue description

See the link to graphs below.
 

Comment 1 by m...@chromium.org, Jul 18 2016

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=629212

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


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

android-nexus9
Project Member

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

Mergedinto: 628120
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : [perf] Change google.com to google.co.uk in top_10_mobile_memory and dual_browser page sets.
Author  : mythria
Commit description:
  
In the top10_mobile page set google.com gets redirected to google.ca. This
sometimes causes problems in telemetry with scrolling. As a short term fix,
replace google.com with google.co.uk in the page set. We cannot change it
to google.ca because memory_top_10_mobile uses the same page set but with
a different wpr that has a recording of google.co.uk. Updated dual_browser
page set to be consistent with top_10_mobile page set.

Also recorded new wprs for memory_top_10_mobile, dual_browser and
top_10_mobile_memory.

BUG= chromium:617914 
LOG=N
CQ_INCLUDE_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq

Review-Url: https://codereview.chromium.org/2138133003
Cr-Commit-Position: refs/heads/master@{#405099}
Commit  : c5acd3851a2f34de15dd89119f0be48c22a9aa72
Date    : Wed Jul 13 09:04:39 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405069  6813213  170051   5  good
chromium@405086  6862053  189249   5  good
chromium@405095  6966039  152607   5  good
chromium@405097  6809915  227982   5  good
chromium@405098  6850486  243965   5  good
chromium@405099  8342572  157082   5  bad    <--
chromium@405103  8208505  388222   5  bad
chromium@405136  8098052  334008   5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 629212

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/http___yandex.ru_touchsearch?text_science
Relative Change: 18.86%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1901
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006765599680689088


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

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

Sign in to add a comment