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

Issue 762228 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
█ briander...@chromium.org
piman@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9%-12.5% regression in smoothness.tough_path_rendering_cases at 499269:499384

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

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

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

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


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

chromium-rel-win10
chromium-rel-win8-dual
Project Member

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


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Stroke Shapes

Revision             Result                  N
chromium@499354      45.8894 +- 8.08259      21      good
chromium@499384      45.9807 +- 7.94494      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=MotionMark.Canvas.Stroke.Shapes smoothness.tough_path_rendering_cases

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

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


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

Comment 6 by 42576172...@developer.gserviceaccount.com, Sep 6 2017 


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Stroke Shapes

Revision             Result                  N
chromium@499354      46.4794 +- 7.29882      21      good
chromium@499384      47.0688 +- 11.567       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=MotionMark.Canvas.Stroke.Shapes smoothness.tough_path_rendering_cases

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

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


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

Comment 7 by 42576172...@developer.gserviceaccount.com, Sep 6 2017

Cc: piman@chromium.org
Owner: piman@chromium.org
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author piman@chromium.org ===

Hi piman@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Antoine Labour
  Commit : 148d0597cb0d72a73c3cc2e481396cb6b24cc535
  Date   : Fri Sep 01 21:00:20 2017
  Subject: Create GrGLInterface based on ui/gl's bindings instead of GrGLAssembleGLInterface

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : smoothness.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Stroke Shapes
  Change       : 0.70% | 47.6677977707 -> 47.3320110449

Revision             Result                   N
chromium@499268      47.6678 +- 2.93926       21      good
chromium@499292      47.7692 +- 1.76763       9       good
chromium@499293      46.8261 +- 0.359598      6       bad       <--
chromium@499294      46.945 +- 3.60503        14      bad
chromium@499295      47.0405 +- 3.10495       9       bad
chromium@499298      46.605 +- 1.20905        6       bad
chromium@499304      46.8513 +- 1.46947       9       bad
chromium@499316      46.9311 +- 2.56016       21      bad
chromium@499364      47.332 +- 3.72857        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=MotionMark.Canvas.Stroke.Shapes smoothness.tough_path_rendering_cases

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

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


For feedback, file a bug with component Speed>Bisection

Comment 8 by sullivan@chromium.org, Sep 6 2017

Owner: ----
Status: WontFix (was: Assigned)
The ref build jumps at the same time as the regression. Maybe a change to the test?
►

Sign in to add a comment