New issue
Advanced search Search tips

Issue 740926 link

Starred by 1 user
Status: Duplicate
Merged: issue 740469
Owner: ----
Closed: Jul 2017
Cc:
ehmaldonado@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.4% regression in webrtc at 484863:484912

Project Member Reported by ehmaldonado@chromium.org, Jul 11 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 11 2017 

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

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


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

android-nexus5X
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jul 12 2017

Mergedinto: 740469
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Dan Elphick
  Commit : 67fac36a35318d03fe141887898821e42dfaecb4
  Date   : Fri Jul 07 08:57:32 2017
  Subject: Increase priority of compositor TQ in NONE Usecase

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : webrtc
  Metric       : cpu_time_percentage_avg/720p_call_45s
  Change       : 3.68% | 0.543719831896 -> 0.563013173211

Revision             Result                     N
chromium@484862      0.54372 +- 0.0110382       9      good
chromium@484863      0.566542 +- 0.0419969      6      bad       <--
chromium@484864      0.559826 +- 0.0242522      6      bad
chromium@484866      0.562133 +- 0.0690898      9      bad
chromium@484869      0.570668 +- 0.0854652      9      bad
chromium@484875      0.562848 +- 0.0373232      6      bad
chromium@484887      0.5649 +- 0.0604646        6      bad
chromium@484912      0.563013 +- 0.0648727      6      bad

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=720p.call.45s webrtc

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

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


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jul 12 2017 


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Dan Elphick
  Commit : 67fac36a35318d03fe141887898821e42dfaecb4
  Date   : Fri Jul 07 08:57:32 2017
  Subject: Increase priority of compositor TQ in NONE Usecase

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : webrtc
  Metric       : cpu_time_percentage_avg/720p_call_45s
  Change       : 1.68% | 0.546768781274 -> 0.555407332823

Revision             Result                     N
chromium@484862      0.546769 +- 0.018454       14      good
chromium@484863      0.559885 +- 0.0339447      9       bad       <--
chromium@484864      0.55681 +- 0.0215415       9       bad
chromium@484866      0.555627 +- 0.0363693      14      bad
chromium@484869      0.555589 +- 0.0517241      21      bad
chromium@484875      0.558606 +- 0.0660874      14      bad
chromium@484887      0.553681 +- 0.0286797      14      bad
chromium@484912      0.555407 +- 0.0145451      9       bad

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=720p.call.45s webrtc

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

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


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment