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

Issue 785568 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.8% regression in thread_times.tough_scrolling_cases at 515545:515624

Project Member Reported by m...@chromium.org, Nov 16 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 16 2017

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

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


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

chromium-rel-win7-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 16 2017


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/canvas_15000_pixels_per_second

Revision             Result                  N
chromium@515544      18.0763 +- 1.47062      21      good
chromium@515624      18.0961 +- 1.05358      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=canvas.15000.pixels.per.second thread_times.tough_scrolling_cases

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 16 2017


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/canvas_15000_pixels_per_second


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=canvas.15000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

Comment 6 by m...@chromium.org, Nov 18 2017

Cc: -m...@chromium.org reve...@chromium.org
Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)
bokan/reveman: This seems related to  bug 785572 , similar tests/issue. However, this is for an earlier rev range. Is this also a WontFix?

Comment 7 by bokan@chromium.org, Nov 20 2017

Status: WontFix (was: Assigned)
Hmm, none of the ranges around the regression have any of my related patches that could have affected this so I'm not sure it's related. That said, it seems to have recovered now so WontFix sounds fine.

Sign in to add a comment