New issue
Advanced search Search tips

Issue 800133 link

Starred by 1 user
Status: Fixed
Owner:
geoffl...@chromium.org
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

88.8% regression in smoothness.gpu_rasterization.tough_path_rendering_cases at 527269:527362

Project Member Reported by benjhayden@chromium.org, Jan 8 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 8 2018 

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

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


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

win-high-dpi

Comment 4 by sullivan@chromium.org, Jan 25 2018 

Re-kicking bisect after temporary fix for large numbers of frame_times metrics.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 25 2018

Cc: waff...@chromium.org tmartino@chromium.org zmo@chromium.org tiborg@chromium.org vollick@chromium.org rkaplow@chromium.org geoffl...@chromium.org
Owner: tmartino@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12e02122840000

Add fieldtrial testing for DefaultPassthroughCommandDecoder.
By geofflang@chromium.org · Fri Jan 05 18:11:20 2018
chromium @ 408921af86e70591ea6f05722e49babb6711ef23

[vr] Update assets component when entering VR and component not ready
By tiborg@chromium.org · Fri Jan 05 19:06:54 2018
chromium @ 8a2c2f916eb0391802d9f4d37be2651d67956f85

Revert "[vr] Update assets component when entering VR and component not ready"
By tmartino@chromium.org · Fri Jan 05 19:30:27 2018
chromium @ 75e3ffd07f6692e7d77e358f1bd0f107f57d2eb6

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 6 by geoffl...@chromium.org, Jan 25 2018

Cc: -vollick@chromium.org -geoffl...@chromium.org -benjhayden@chromium.org -tmartino@chromium.org -waff...@chromium.org -tiborg@chromium.org -zmo@chromium.org -rkaplow@chromium.org
Owner: geoffl...@chromium.org

Comment 7 by vmi...@chromium.org, Feb 5 2018

Components: Internals>GPU>Metrics
Project Member

Comment 8 by bugdroid1@chromium.org, Apr 23 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/54605398cbde33a08290af8a7457590602dfb0b4

commit 54605398cbde33a08290af8a7457590602dfb0b4
Author: Geoff Lang <geofflang@chromium.org>
Date: Mon Apr 23 19:37:59 2018

Implement the msaa_is_slow and avoid_stencil_buffers gpu capabilities.

These capabitilites were not implemented in the passthrough command decoder
which resulted in poor MSAA performace on Intel high DPI.

BUG= 801659 
BUG= 800133 
BUG= 800011 
BUG= 799951 

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I2e1f0f3b4b8267421646279b6d3154223f8199b0
Reviewed-on: https://chromium-review.googlesource.com/1024282
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#552794}
[modify] https://crrev.com/54605398cbde33a08290af8a7457590602dfb0b4/gpu/command_buffer/service/gles2_cmd_decoder_passthrough.cc

Comment 9 by geoffl...@chromium.org, Apr 25 2018

Status: Fixed (was: Assigned)
►

Sign in to add a comment