See the link to graphs below.
All graphs for this bug: https://chromeperf.appspot.com/group_report?bug_id=911975 (For debugging:) Original alerts at time of bug-filing: https://chromeperf.appspot.com/group_report?sid=af69757e8bf7a8014ac972385a0c159c6d10acdb58aa35c48054a7191cba4e87 Bot(s) for this bug's original alert(s): Win 7 Nvidia GPU Perf rendering.desktop - Benchmark documentation link: https://bit.ly/rendering-benchmarks
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15e84e10140000
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/15e84e10140000 Register fling scheduler on GSB instead of GFS. by sahel@chromium.org https://chromium.googlesource.com/chromium/src/+/0e58f2caab6a230fdb0f2b1993a44c2f4546c2f5 tasks_per_frame_total_all: 51.24 → 66.08 (+14.83) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0996ec8f771b7c0cc28aa56b201abf3ace2d4176 commit 0996ec8f771b7c0cc28aa56b201abf3ace2d4176 Author: Sahel Sharify <sahel@chromium.org> Date: Fri Dec 07 17:19:41 2018 Revert "Register fling scheduler on GSB instead of GFS." Revert "Register fling scheduler on GSB instead of GFS." and Revert "Fixed fling regression from registering observer on GSB instead of GFS." This reverts the following two commits: 0b48b62c4392e7cd594d9fbe8684e93abc72aa1b 0e58f2caab6a230fdb0f2b1993a44c2f4546c2f5 The reason for reverting is that registering fling scheduler observer on GSB instead of GFS does not fix the one frame jank at the beginning of the fling. This change also caused some performance regressions and touchpad scrolling regression on eve. Bug: 882907, 911975 , 911334 ,903161,903156, 903155 Change-Id: I6aba2c0314eeab616fcb1c18c448c0b3c075d4e6 Reviewed-on: https://chromium-review.googlesource.com/c/1363893 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#614730} [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_controller.cc [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_controller.h [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_controller_unittest.cc [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_scheduler.cc [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_scheduler.h [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_scheduler_android.cc [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_scheduler_android.h [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/fling_scheduler_unittest.cc [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/gesture_event_queue.cc [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/gesture_event_queue_unittest.cc [modify] https://crrev.com/0996ec8f771b7c0cc28aa56b201abf3ace2d4176/content/browser/renderer_host/input/mock_input_router_client.h
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20 commit 3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20 Author: Sahel Sharify <sahel@chromium.org> Date: Tue Dec 11 21:28:04 2018 Revert "Register fling scheduler on GSB instead of GFS." Revert "Register fling scheduler on GSB instead of GFS." and Revert "Fixed fling regression from registering observer on GSB instead of GFS." This reverts the following two commits: 0b48b62c4392e7cd594d9fbe8684e93abc72aa1b 0e58f2caab6a230fdb0f2b1993a44c2f4546c2f5 The reason for reverting is that registering fling scheduler observer on GSB instead of GFS does not fix the one frame jank at the beginning of the fling. This change also caused some performance regressions and touchpad scrolling regression on eve. Bug: 882907, 911975 , 911334 ,903161,903156, 903155 Change-Id: I6aba2c0314eeab616fcb1c18c448c0b3c075d4e6 Reviewed-on: https://chromium-review.googlesource.com/c/1363893 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#614730}(cherry picked from commit 0996ec8f771b7c0cc28aa56b201abf3ace2d4176) Reviewed-on: https://chromium-review.googlesource.com/c/1372714 Reviewed-by: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/branch-heads/3626@{#262} Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437} [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_controller.cc [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_controller.h [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_controller_unittest.cc [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_scheduler.cc [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_scheduler.h [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_scheduler_android.cc [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_scheduler_android.h [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/fling_scheduler_unittest.cc [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/gesture_event_queue.cc [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/gesture_event_queue_unittest.cc [modify] https://crrev.com/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20/content/browser/renderer_host/input/mock_input_router_client.h
The graph has recovered after the revert.
The regression has recovered after the revert.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20 Commit: 3cc06e54913c18ff3a45e9dda912bc7b5e5d5e20 Author: sahel@chromium.org Commiter: bokan@chromium.org Date: 2018-12-11 21:28:04 +0000 UTC Revert "Register fling scheduler on GSB instead of GFS." Revert "Register fling scheduler on GSB instead of GFS." and Revert "Fixed fling regression from registering observer on GSB instead of GFS." This reverts the following two commits: 0b48b62c4392e7cd594d9fbe8684e93abc72aa1b 0e58f2caab6a230fdb0f2b1993a44c2f4546c2f5 The reason for reverting is that registering fling scheduler observer on GSB instead of GFS does not fix the one frame jank at the beginning of the fling. This change also caused some performance regressions and touchpad scrolling regression on eve. Bug: 882907, 911975 , 911334 ,903161,903156, 903155 Change-Id: I6aba2c0314eeab616fcb1c18c448c0b3c075d4e6 Reviewed-on: https://chromium-review.googlesource.com/c/1363893 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#614730}(cherry picked from commit 0996ec8f771b7c0cc28aa56b201abf3ace2d4176) Reviewed-on: https://chromium-review.googlesource.com/c/1372714 Reviewed-by: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/branch-heads/3626@{#262} Cr-Branched-From: d897fb137fbaaa9355c0c93124cc048824eb1e65-refs/heads/master@{#612437}
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 5