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

Issue 797415 link

Starred by 1 user
Status: Duplicate
Merged: issue 797065
Owner:
beccahughes@chromium.org
Closed: Jan 2018
Cc:
█ briander...@chromium.org
catapult-deps-roller@chromium.org
beccahughes@chromium.org
mlamouri@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.7% regression in system_health.common_mobile at 524706:524787

Project Member Reported by briander...@chromium.org, Dec 22 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 22 2017 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=7b91f89cb15364b1df29936285aab74bfe7951a4948b0f671427cefabb020817


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 22 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/browse_news/browse_news_cnn


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn system_health.common_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8959470692148538720


For feedback, file a bug with component Speed>Bisection

Comment 5 by sullivan@chromium.org, Jan 24 2018 

Most of these came back down; trying one more bisect on cpu_time_percentage_avg
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jan 24 2018

Cc: catapult-deps-roller@chromium.org beccahughes@chromium.org mlamouri@chromium.org
Owner: beccahughes@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14de420c840000

Roll src/third_party/catapult/ 6c84ef000..8a4ac91dd (1 commit)
By catapult-deps-roller@chromium.org · Mon Dec 18 13:51:46 2017
chromium @ 97b283f950a14bad9ff01b8a47911531589fba40

Media Engagement: Move record scores histo to task runner
By beccahughes@chromium.org · Mon Dec 18 14:29:44 2017
chromium @ e505f9db8ab902f50b16368498198f8f74a8d13c

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 7 by mlamouri@chromium.org, Jan 25 2018 

The culprit CL landed to resolve another performance issue:  bug 791779 . Do you have any recommendations that wouldn't regress  bug 791779 ?

Comment 8 by dtu@chromium.org, Jan 26 2018 

Looks like the catapult roll is the cause for the bulk of the regression here. It contains one commit.

Disable autoplay restrictions on Chrome via command line flag.
catapult @ 8a4ac91dd3927e5edb725d452775055a695fa62d

Comment 9 by mlamouri@chromium.org, Jan 26 2018

Mergedinto: 797065
Status: Duplicate (was: Assigned)
In that case, this bug is a dup of  bug 797065 .
►

Sign in to add a comment