New issue
Advanced search Search tips

Issue 765123 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Dec 2017
Cc:
toyoshim@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

19.8%-3043% regression in performance_browser_tests at 500297:501404

Project Member Reported by toyoshim@chromium.org, Sep 14 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 14 2017 

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 14 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : CastV2Performance_gpu_30fps_bad/audio_jitter

Revision             Result                   N
chromium@500296      0.720804 +- 4.37729      21      good
chromium@501404      0.863202 +- 4.53977      21      bad

To Run This Test
  .\src\out\Release\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 15 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : CastV2Performance_gpu_30fps_bad/time_between_captures

Revision             Result                   N
chromium@500296      33.4526 +- 0.467111      21      good
chromium@501404      33.4877 +- 0.495314      21      bad

To Run This Test
  .\src\out\Release\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


For feedback, file a bug with component Speed>Bisection

Comment 6 by npm@chromium.org, Dec 7 2017

Status: Fixed (was: Untriaged)
Graphs show that the regression was fixed.
►

Sign in to add a comment